Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbe4dcc0a9c25081fc41cb1d289c6a23f32aaf7e1dbeff96b881232442538b20

Tx prefix hash: bf22583c8fe1c039b50aefb3a6f66e7bb7556085633f90f2b5b658e6fd027058
Tx public key: 9c3e601632f276ef9a5a7adddc9b43388853483e287d7a459668913fa335d74b
Timestamp: 1715185533 Timestamp [UCT]: 2024-05-08 16:25:33 Age [y:d:h:m:s]: 00:281:04:49:25
Block: 1017656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200973 RingCT/type: yes/0
Extra: 019c3e601632f276ef9a5a7adddc9b43388853483e287d7a459668913fa335d74b0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4e1ac0e21e42f4a7c6fb6b24c72a990f159590490083fe782c12f0cd49a1277 0.600000000000 1481439 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": 1017666, "vin": [ { "gen": { "height": 1017656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4e1ac0e21e42f4a7c6fb6b24c72a990f159590490083fe782c12f0cd49a1277" } } ], "extra": [ 1, 156, 62, 96, 22, 50, 242, 118, 239, 154, 90, 122, 221, 220, 155, 67, 56, 136, 83, 72, 62, 40, 125, 122, 69, 150, 104, 145, 63, 163, 53, 215, 75, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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