Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4019f107cf80640669fb490e2a9e80d3e54cb85af8b308f643ed74e5cf69e4b7

Tx prefix hash: 8fc3f75048f908ee7f9207dd3da8025742dd3c7f672b1646d25e5cd884213b9d
Tx public key: 01235417fcf48b8af158db840ed087b6fd2123e34015d5f72af62c7c7573374e
Timestamp: 1735125198 Timestamp [UCT]: 2024-12-25 11:13:18 Age [y:d:h:m:s]: 00:088:15:55:30
Block: 1182837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63133 RingCT/type: yes/0
Extra: 0101235417fcf48b8af158db840ed087b6fd2123e34015d5f72af62c7c7573374e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a27aa1e396ab32aa5fcd60f533f5ddb8ecb8610e0cc26702231f8643d150d058 0.600000000000 1669276 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": 1182847, "vin": [ { "gen": { "height": 1182837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a27aa1e396ab32aa5fcd60f533f5ddb8ecb8610e0cc26702231f8643d150d058" } } ], "extra": [ 1, 1, 35, 84, 23, 252, 244, 139, 138, 241, 88, 219, 132, 14, 208, 135, 182, 253, 33, 35, 227, 64, 21, 213, 247, 42, 246, 44, 124, 117, 115, 55, 78, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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