Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0218e6a88312693831fe6019f6512f10c6458e7aa1b9db3501c9a8b3710b6c1

Tx prefix hash: fd34525baec43474382d443774febc15102e9c62ad04e7b21ddcf674a557ff3a
Tx public key: 8ae0ec22e0a5b133125c876696e9092b92ee1874038949aa781c46e0ddcecade
Timestamp: 1730197893 Timestamp [UCT]: 2024-10-29 10:31:33 Age [y:d:h:m:s]: 00:165:10:01:47
Block: 1142041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118045 RingCT/type: yes/0
Extra: 018ae0ec22e0a5b133125c876696e9092b92ee1874038949aa781c46e0ddcecade021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecab94cf32fed8861e24f65ea1cd71501f26c87fcd7a0b6b56a8ae0d56b73b5c 0.600000000000 1625876 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": 1142051, "vin": [ { "gen": { "height": 1142041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecab94cf32fed8861e24f65ea1cd71501f26c87fcd7a0b6b56a8ae0d56b73b5c" } } ], "extra": [ 1, 138, 224, 236, 34, 224, 165, 177, 51, 18, 92, 135, 102, 150, 233, 9, 43, 146, 238, 24, 116, 3, 137, 73, 170, 120, 28, 70, 224, 221, 206, 202, 222, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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