Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb42f9b8ea47e7816e5f969f88e4cc018f073de74147f4847f651db00176fd43

Tx prefix hash: 915487fb8346b18aa083cd845306a506d6648c0e87f86fab072ceb1e72f259e6
Tx public key: aa4a200abb40ca38b2f22d36d98ad578a4c21598bdc4c9f94f7ab6cea52c99d4
Timestamp: 1708573547 Timestamp [UCT]: 2024-02-22 03:45:47 Age [y:d:h:m:s]: 00:337:02:54:32
Block: 962825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241287 RingCT/type: yes/0
Extra: 01aa4a200abb40ca38b2f22d36d98ad578a4c21598bdc4c9f94f7ab6cea52c99d402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39bf7d02fa3a944536810d08d24d2408092143e41ed06223ccd2c2a1a9a18309 0.600000000000 1422510 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": 962835, "vin": [ { "gen": { "height": 962825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39bf7d02fa3a944536810d08d24d2408092143e41ed06223ccd2c2a1a9a18309" } } ], "extra": [ 1, 170, 74, 32, 10, 187, 64, 202, 56, 178, 242, 45, 54, 217, 138, 213, 120, 164, 194, 21, 152, 189, 196, 201, 249, 79, 122, 182, 206, 165, 44, 153, 212, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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