Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 480d25f4ee5e88e8a2a2a7b45bb8d7d48b06adf3f3c7399d6278abc3d3a763e0

Tx prefix hash: 3c0c9a0a479e223ea20d7823419ec32341e4c40336997ae1c9877b1a56cb062b
Tx public key: f61a2d83a1834024dd461e8f405b28e5f95a0770de8d5b142d07b0ad0e70e846
Timestamp: 1708873282 Timestamp [UCT]: 2024-02-25 15:01:22 Age [y:d:h:m:s]: 01:058:17:10:48
Block: 965317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302986 RingCT/type: yes/0
Extra: 01f61a2d83a1834024dd461e8f405b28e5f95a0770de8d5b142d07b0ad0e70e8460211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c80df3303de6262a6055655730e9361a06cd8991fabce2175388b953e4d8ece 0.600000000000 1425066 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": 965327, "vin": [ { "gen": { "height": 965317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c80df3303de6262a6055655730e9361a06cd8991fabce2175388b953e4d8ece" } } ], "extra": [ 1, 246, 26, 45, 131, 161, 131, 64, 36, 221, 70, 30, 143, 64, 91, 40, 229, 249, 90, 7, 112, 222, 141, 91, 20, 45, 7, 176, 173, 14, 112, 232, 70, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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