Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae17578221d37d264b1753a266c3a830eb604bb4b097e4900ebcfe47916b1479

Tx prefix hash: f0d8b106a599a953c75f476aa92a3b67a2aa203e1fbcd92a56506653489f2c65
Tx public key: c363e0261c42b2283dc894f2eb97b1785eb6970686e9ee3061e5738b5fd3dc84
Timestamp: 1746438514 Timestamp [UCT]: 2025-05-05 09:48:34 Age [y:d:h:m:s]: 00:191:07:07:31
Block: 1276214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134429 RingCT/type: yes/0
Extra: 01c363e0261c42b2283dc894f2eb97b1785eb6970686e9ee3061e5738b5fd3dc840211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f318b720ae6c372066714a403dfe71aa7428d16624e86615b93773ac4d1be0d7 0.600000000000 1763539 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 dinasty-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": 1276224, "vin": [ { "gen": { "height": 1276214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f318b720ae6c372066714a403dfe71aa7428d16624e86615b93773ac4d1be0d7" } } ], "extra": [ 1, 195, 99, 224, 38, 28, 66, 178, 40, 61, 200, 148, 242, 235, 151, 177, 120, 94, 182, 151, 6, 134, 233, 238, 48, 97, 229, 115, 139, 95, 211, 220, 132, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8