Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b34e955bd09721163915522efa699701c17dc7b28bfbee2f56cba2cb4331da1

Tx prefix hash: 15c76ccd8e56a9e654e0d086a7b435ad1aa523bcf3b959fb27648d73dcd71511
Tx public key: f8a255834d85f4d91867631b0657c9d3102422b8bf688c642f9bf6e01f3a446a
Timestamp: 1717737248 Timestamp [UCT]: 2024-06-07 05:14:08 Age [y:d:h:m:s]: 00:302:23:25:49
Block: 1038797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216527 RingCT/type: yes/0
Extra: 01f8a255834d85f4d91867631b0657c9d3102422b8bf688c642f9bf6e01f3a446a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 233513b1ef1a5dcd6e961672eb389338909f6b16f8a68ad871877c7ff359782c 0.600000000000 1507358 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": 1038807, "vin": [ { "gen": { "height": 1038797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "233513b1ef1a5dcd6e961672eb389338909f6b16f8a68ad871877c7ff359782c" } } ], "extra": [ 1, 248, 162, 85, 131, 77, 133, 244, 217, 24, 103, 99, 27, 6, 87, 201, 211, 16, 36, 34, 184, 191, 104, 140, 100, 47, 155, 246, 224, 31, 58, 68, 106, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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