Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed10227799b52ed13c3bbf217fd81fc37218d78a885a181205a2700dddcf61ea

Tx prefix hash: bb3c095f0bf785c3f603ed22c8cd80e8ce97106cc4e8feea687c4ba7e4dab3be
Tx public key: e3ebe9a99b3ef48989569ebd659a52d3b5a555b582cf0826e0ec8c3d64113329
Timestamp: 1772266458 Timestamp [UTC]: 2026-02-28 08:14:18 Age [y:d:h:m:s]: 00:178:00:51:53
Block: 1487498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133074 RingCT/type: yes/0
Extra: 01e3ebe9a99b3ef48989569ebd659a52d3b5a555b582cf0826e0ec8c3d64113329021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3227134b19566e02c3aca3ce0f1849bf0304691ab95f7263e741c38de09c4f2e 0.000600000000 1976968 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": 1487508, "vin": [ { "gen": { "height": 1487498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3227134b19566e02c3aca3ce0f1849bf0304691ab95f7263e741c38de09c4f2e" } } ], "extra": [ 1, 227, 235, 233, 169, 155, 62, 244, 137, 137, 86, 158, 189, 101, 154, 82, 211, 181, 165, 85, 181, 130, 207, 8, 38, 224, 236, 140, 61, 100, 17, 51, 41, 2, 17, 0, 0, 0, 3, 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: