Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fad2c7583d3755d76ce56ff80c8f7e3cba001dfbc6d74f3d5d54be03fcedbcd3

Tx prefix hash: b036fb434e37700db0ff2e14768c518bb57ed32f36522c7064732ec0cafefdb5
Tx public key: 8aa590f7c34b0b9d5df8a26f7125b5da3256b4c86b227c496a1a69a73bf5e19d
Timestamp: 1713074283 Timestamp [UCT]: 2024-04-14 05:58:03 Age [y:d:h:m:s]: 01:011:08:52:50
Block: 1000116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269100 RingCT/type: yes/0
Extra: 018aa590f7c34b0b9d5df8a26f7125b5da3256b4c86b227c496a1a69a73bf5e19d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a22a6c6484a2d0e2d40d17d73a6eec8d17aa0ff3c6afa2907071053d65d5cc5 0.600000000000 1460608 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": 1000126, "vin": [ { "gen": { "height": 1000116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a22a6c6484a2d0e2d40d17d73a6eec8d17aa0ff3c6afa2907071053d65d5cc5" } } ], "extra": [ 1, 138, 165, 144, 247, 195, 75, 11, 157, 93, 248, 162, 111, 113, 37, 181, 218, 50, 86, 180, 200, 107, 34, 124, 73, 106, 26, 105, 167, 59, 245, 225, 157, 2, 17, 0, 0, 0, 2, 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