Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ae6a3cb98d0205347388ce4a9423f93affeac003204d4aa40f706756cb4d28c

Tx prefix hash: 104775bb231aaf543031a2a45c44e6c7cfbcc9c5668fed79dce6189eb6434810
Tx public key: f1a62c71fcdd7d30f1a5af3b33c97baea204ff3bfb9b51a1c94dae0fbf128f49
Timestamp: 1696768804 Timestamp [UCT]: 2023-10-08 12:40:04 Age [y:d:h:m:s]: 01:169:21:37:50
Block: 865168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382442 RingCT/type: yes/0
Extra: 01f1a62c71fcdd7d30f1a5af3b33c97baea204ff3bfb9b51a1c94dae0fbf128f49021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.834332771000 dcy

stealth address amount amount idx
00: 1102f817d82d5d65911b6ccab42721ee6f439bdf950ac5bbc2ac8e6e2c08b5a8 0.834332771000 1319694 of 0

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": 865178, "vin": [ { "gen": { "height": 865168 } } ], "vout": [ { "amount": 834332771, "target": { "key": "1102f817d82d5d65911b6ccab42721ee6f439bdf950ac5bbc2ac8e6e2c08b5a8" } } ], "extra": [ 1, 241, 166, 44, 113, 252, 221, 125, 48, 241, 165, 175, 59, 51, 201, 123, 174, 162, 4, 255, 59, 251, 155, 81, 161, 201, 77, 174, 15, 191, 18, 143, 73, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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