Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bd281643dcde67895d530a2d55c8147b43161c02e00406debfeafe646cd0857a

Tx prefix hash: 63dcaa6237503d90a0fc92d4a7df8b2722ed3d1c0f74d03d5493b9f2c01aecf2
Tx public key: a293ed0b50fa3ba704cf9b88ca00758190aafe0da6f89b11c0533f68d020daaa
Timestamp: 1578289061 Timestamp [UTC]: 2020-01-06 05:37:41 Age [y:d:h:m:s]: 06:136:07:47:30
Block: 39584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1499434 RingCT/type: yes/0
Extra: 01a293ed0b50fa3ba704cf9b88ca00758190aafe0da6f89b11c0533f68d020daaa021100000001b221b3d1000000000000000000

1 output(s) for total of 0.453784981036 xmr

stealth address amount amount idx tag
00: 041af83e6930cceb0e0e10b77f34ddb7f4eab6b84647e0473cfec434da6763f8 0.453784981036 68539 of 0 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 39594, "vin": [ { "gen": { "height": 39584 } } ], "vout": [ { "amount": 453784981036, "target": { "key": "041af83e6930cceb0e0e10b77f34ddb7f4eab6b84647e0473cfec434da6763f8" } } ], "extra": [ 1, 162, 147, 237, 11, 80, 250, 59, 167, 4, 207, 155, 136, 202, 0, 117, 129, 144, 170, 254, 13, 166, 248, 155, 17, 192, 83, 63, 104, 208, 32, 218, 170, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: