Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae981406ed2a58a35226aa7d426705080e793d4fcf8ea7d74e8a5bb0181812a4

Tx prefix hash: 760336a51bb7ce98a0aad521303eb44ace9dfafbd01b99e7a0943c984701e023
Tx public key: 6dbff791ea9d6b77dcdb0725cb98d24917ff91d363fec988cad7ebb219560704
Timestamp: 1772096152 Timestamp [UTC]: 2026-02-26 08:55:52 Age [y:d:h:m:s]: 00:266:19:38:50
Block: 1486080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196319 RingCT/type: yes/0
Extra: 016dbff791ea9d6b77dcdb0725cb98d24917ff91d363fec988cad7ebb219560704021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 461d4432a04a95c42a1ec9212603452840d0f6f80f39ca4752f646c8c1ccf4d5 0.000600000000 1975524 of 15 -

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": 1486090, "vin": [ { "gen": { "height": 1486080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "461d4432a04a95c42a1ec9212603452840d0f6f80f39ca4752f646c8c1ccf4d5" } } ], "extra": [ 1, 109, 191, 247, 145, 234, 157, 107, 119, 220, 219, 7, 37, 203, 152, 210, 73, 23, 255, 145, 211, 99, 254, 201, 136, 202, 215, 235, 178, 25, 86, 7, 4, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 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: