Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6fb06fc0535bf4dd430300cbfaa4d4b3c8443dbcbcd1f4ea9961cd25669a2bd

Tx prefix hash: f9c6ddbb7f0409faa48384ca93b68879918cfbca214f067ab398cba3dfdb9dda
Tx public key: 77e84c9d42154c17307477f7c7b237da4fd4fd5c6c632cb4fe59acfbf97a6e01
Timestamp: 1702097554 Timestamp [UCT]: 2023-12-09 04:52:34 Age [y:d:h:m:s]: 01:190:09:38:04
Block: 909124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397176 RingCT/type: yes/0
Extra: 0177e84c9d42154c17307477f7c7b237da4fd4fd5c6c632cb4fe59acfbf97a6e01021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4fb023c64048b2332863d900031e3ccfb59809733072b3e020e239ee680a379 0.600000000000 1366189 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": 909134, "vin": [ { "gen": { "height": 909124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4fb023c64048b2332863d900031e3ccfb59809733072b3e020e239ee680a379" } } ], "extra": [ 1, 119, 232, 76, 157, 66, 21, 76, 23, 48, 116, 119, 247, 199, 178, 55, 218, 79, 212, 253, 92, 108, 99, 44, 180, 254, 89, 172, 251, 249, 122, 110, 1, 2, 17, 0, 0, 0, 4, 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