Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c55e29a0dfe356df79f9e5bdb59915230d4adc216219d10dd17126bf56481217

Tx prefix hash: 883b83b700f8d1588f582c4cb52c686b13e60f14698f8e1cfd19dfe5804cb3de
Tx public key: 510a497f2622c4c9e44eb94205f139c5f76499f8ce8c0f94ac0c7b46be1caa3c
Timestamp: 1727103822 Timestamp [UCT]: 2024-09-23 15:03:42 Age [y:d:h:m:s]: 00:106:08:00:02
Block: 1116446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76030 RingCT/type: yes/0
Extra: 01510a497f2622c4c9e44eb94205f139c5f76499f8ce8c0f94ac0c7b46be1caa3c021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c9bd2e10e6608ed45335911132f3ae55a2c86a32dd5889b8e1f77e341558113 0.600000000000 1596929 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": 1116456, "vin": [ { "gen": { "height": 1116446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c9bd2e10e6608ed45335911132f3ae55a2c86a32dd5889b8e1f77e341558113" } } ], "extra": [ 1, 81, 10, 73, 127, 38, 34, 196, 201, 228, 78, 185, 66, 5, 241, 57, 197, 247, 100, 153, 248, 206, 140, 15, 148, 172, 12, 123, 70, 190, 28, 170, 60, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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