Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ad135da7c17fe12028d53861639546492f122eb86f78bdf97845bd493f4185a

Tx prefix hash: 871035bcb6f9134387fe37baff8f149ef0aa271ec31d72b9dc7d82927a06f63b
Tx public key: 5be045966ad9ee295d8be7e8a9afbe1393380d8ec9bdc8125e2dbb5e7e48f0ca
Timestamp: 1733323656 Timestamp [UCT]: 2024-12-04 14:47:36 Age [y:d:h:m:s]: 00:346:08:35:53
Block: 1167909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245078 RingCT/type: yes/0
Extra: 015be045966ad9ee295d8be7e8a9afbe1393380d8ec9bdc8125e2dbb5e7e48f0ca0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d10913cc14aa2a7c1677b50ac6b1a2094ebf78554e1b310fc001bcc0c1d9c16 0.600000000000 1653614 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": 1167919, "vin": [ { "gen": { "height": 1167909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d10913cc14aa2a7c1677b50ac6b1a2094ebf78554e1b310fc001bcc0c1d9c16" } } ], "extra": [ 1, 91, 224, 69, 150, 106, 217, 238, 41, 93, 139, 231, 232, 169, 175, 190, 19, 147, 56, 13, 142, 201, 189, 200, 18, 94, 45, 187, 94, 126, 72, 240, 202, 2, 17, 0, 0, 0, 2, 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