Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a810c517da0884a0b72f087b2be31b3b303b7b24dfeb43880201b810d3a4f669

Tx prefix hash: 0e405920047d36b73627059af8a98bfc5c7039c546128d7dcadfa7be0bb7ff90
Tx public key: 17e8a3ff0e3f8d1e3fcce94899f1fe20f3b40c3329a4220cb87a6e4e603fd264
Timestamp: 1695563989 Timestamp [UCT]: 2023-09-24 13:59:49 Age [y:d:h:m:s]: 01:261:06:43:37
Block: 855168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447830 RingCT/type: yes/0
Extra: 0117e8a3ff0e3f8d1e3fcce94899f1fe20f3b40c3329a4220cb87a6e4e603fd264021100000001faf35c9c000000000000000000

1 output(s) for total of 0.900478749000 dcy

stealth address amount amount idx
00: 9e73149a5275cf6523b2894296ef0234ed3038df4496b5b2f6c72970866ddae6 0.900478749000 1309172 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": 855178, "vin": [ { "gen": { "height": 855168 } } ], "vout": [ { "amount": 900478749, "target": { "key": "9e73149a5275cf6523b2894296ef0234ed3038df4496b5b2f6c72970866ddae6" } } ], "extra": [ 1, 23, 232, 163, 255, 14, 63, 141, 30, 63, 204, 233, 72, 153, 241, 254, 32, 243, 180, 12, 51, 41, 164, 34, 12, 184, 122, 110, 78, 96, 63, 210, 100, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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