Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40022f9b38bd3d79472fcd3b9ed1f25fd95d671be23767a0651ce5748a4946f4

Tx prefix hash: 4d6d19ee880b3385e1ede7187b860c015365642b0e992db7cd926e70defe76f2
Tx public key: b33b2a928a12992ac4dc89665481e4e827c9f7d57fd2dfd0587781434077b164
Timestamp: 1724093228 Timestamp [UCT]: 2024-08-19 18:47:08 Age [y:d:h:m:s]: 00:261:22:33:38
Block: 1091495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187081 RingCT/type: yes/0
Extra: 01b33b2a928a12992ac4dc89665481e4e827c9f7d57fd2dfd0587781434077b16402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18ad53819c20933eb09c75563ae6b822ad23a140c536bf3f2c44e6c7e903def0 0.600000000000 1566128 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": 1091505, "vin": [ { "gen": { "height": 1091495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18ad53819c20933eb09c75563ae6b822ad23a140c536bf3f2c44e6c7e903def0" } } ], "extra": [ 1, 179, 59, 42, 146, 138, 18, 153, 42, 196, 220, 137, 102, 84, 129, 228, 232, 39, 201, 247, 213, 127, 210, 223, 208, 88, 119, 129, 67, 64, 119, 177, 100, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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