Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf24ade8801045ca92ccffc0fd61f2607464939ac5ae496155c92e8445eebaaa

Tx prefix hash: ac94504e2d756f30806250ac18ae591902e0bceea85479985b4b0780f1e820a7
Tx public key: 3443d90a8c034a9b93901e21752e1c57ea8740c95e7a6ba3d828ae1a28d7b163
Timestamp: 1740091906 Timestamp [UCT]: 2025-02-20 22:51:46 Age [y:d:h:m:s]: 00:344:21:34:03
Block: 1223659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244187 RingCT/type: yes/0
Extra: 013443d90a8c034a9b93901e21752e1c57ea8740c95e7a6ba3d828ae1a28d7b163021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed18cfecc07941bcfb91e0df7413a11599bdb937cef57265ae7fc25fff025593 0.600000000000 1710516 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": 1223669, "vin": [ { "gen": { "height": 1223659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed18cfecc07941bcfb91e0df7413a11599bdb937cef57265ae7fc25fff025593" } } ], "extra": [ 1, 52, 67, 217, 10, 140, 3, 74, 155, 147, 144, 30, 33, 117, 46, 28, 87, 234, 135, 64, 201, 94, 122, 107, 163, 216, 40, 174, 26, 40, 215, 177, 99, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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