Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecab43bb0e2730ef071280172c7e60891a21d57007a5b0325490d861c1f7ba7b

Tx prefix hash: 22912a875abe508af59bd4c74cb47e3029c103956f8499d01d4ed8e551b8acdd
Tx public key: df3ea7f4d042a5d58e77d76210ed99d527faa0ee835d0e1bda4c8aab4806c7ef
Timestamp: 1705229497 Timestamp [UCT]: 2024-01-14 10:51:37 Age [y:d:h:m:s]: 01:134:18:41:04
Block: 935094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357456 RingCT/type: yes/0
Extra: 01df3ea7f4d042a5d58e77d76210ed99d527faa0ee835d0e1bda4c8aab4806c7ef02110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 126c54df13514e0c187ce144fa79cb0f3dcac1da47d9bd618c354cd73865d3f2 0.600000000000 1393110 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": 935104, "vin": [ { "gen": { "height": 935094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "126c54df13514e0c187ce144fa79cb0f3dcac1da47d9bd618c354cd73865d3f2" } } ], "extra": [ 1, 223, 62, 167, 244, 208, 66, 165, 213, 142, 119, 215, 98, 16, 237, 153, 213, 39, 250, 160, 238, 131, 93, 14, 27, 218, 76, 138, 171, 72, 6, 199, 239, 2, 17, 0, 0, 0, 12, 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