Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b26ebcaf7f002ac0cfa5f4e851d6752c794e7eaecfe07a624daec2c17c84ce4

Tx prefix hash: 9ae789246e73311e428a519be7a8b983720d6e0113506eeedc9555746bde5ddc
Tx public key: 3acf18990cdd397d6c6f4a09da3bb25d401a19c39e7db55677d51737e521776f
Timestamp: 1713586983 Timestamp [UCT]: 2024-04-20 04:23:03 Age [y:d:h:m:s]: 00:351:10:56:57
Block: 1004369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251256 RingCT/type: yes/0
Extra: 013acf18990cdd397d6c6f4a09da3bb25d401a19c39e7db55677d51737e521776f0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77e22a69b72fd3443f718d5937c1b53b74e817d4d14834c38cdb42a4e740ac0e 0.600000000000 1464937 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": 1004379, "vin": [ { "gen": { "height": 1004369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77e22a69b72fd3443f718d5937c1b53b74e817d4d14834c38cdb42a4e740ac0e" } } ], "extra": [ 1, 58, 207, 24, 153, 12, 221, 57, 125, 108, 111, 74, 9, 218, 59, 178, 93, 64, 26, 25, 195, 158, 125, 181, 86, 119, 213, 23, 55, 229, 33, 119, 111, 2, 17, 0, 0, 0, 8, 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