Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e5bde3bf4fbdbb82b19543344ac4dff347173d9272e728c393bba6f31d32e35

Tx prefix hash: 434fe8042d03d8f5cf161a6c1a65a6b34436333614531c649f76dcd880a6a2b6
Tx public key: 378dc789c5251b9d6b6d24b9746fa8fdf6b95e509b5807cae73802d8e686c451
Timestamp: 1702328842 Timestamp [UCT]: 2023-12-11 21:07:22 Age [y:d:h:m:s]: 01:334:07:01:56
Block: 911058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497774 RingCT/type: yes/0
Extra: 01378dc789c5251b9d6b6d24b9746fa8fdf6b95e509b5807cae73802d8e686c4510211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4a711089111e5fe9cb0ca1bac076ee5bdb27cec8bf12cf2af97fac791feb744 0.600000000000 1368233 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": 911068, "vin": [ { "gen": { "height": 911058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4a711089111e5fe9cb0ca1bac076ee5bdb27cec8bf12cf2af97fac791feb744" } } ], "extra": [ 1, 55, 141, 199, 137, 197, 37, 27, 157, 107, 109, 36, 185, 116, 111, 168, 253, 246, 185, 94, 80, 155, 88, 7, 202, 231, 56, 2, 216, 230, 134, 196, 81, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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