Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d207a8b42d0bfd2f53e781f51d6461cbbeb85f73a3bfbf8b76f96b571bdd4579

Tx prefix hash: a008c3eacdc4ad9b3a0a5741a30922c75712c41c61b6ea141bd2ba47a042ad66
Tx public key: 9da96f3dfaa8a6c82052610a223af8abeef9aa61a8510d31aaacc5d7a5cc2792
Timestamp: 1742498884 Timestamp [UTC]: 2025-03-20 19:28:04 Age [y:d:h:m:s]: 01:242:15:04:19
Block: 1243624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437443 RingCT/type: yes/0
Extra: 019da96f3dfaa8a6c82052610a223af8abeef9aa61a8510d31aaacc5d7a5cc2792021100000004ed95dce7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0d296784a6b1c2cb1a2d02cd08b67a471a516eaa78828162c8a953e75c7571ed 0.000600000000 1730609 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": 1243634, "vin": [ { "gen": { "height": 1243624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d296784a6b1c2cb1a2d02cd08b67a471a516eaa78828162c8a953e75c7571ed" } } ], "extra": [ 1, 157, 169, 111, 61, 250, 168, 166, 200, 32, 82, 97, 10, 34, 58, 248, 171, 238, 249, 170, 97, 168, 81, 13, 49, 170, 172, 197, 215, 165, 204, 39, 146, 2, 17, 0, 0, 0, 4, 237, 149, 220, 231, 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: