Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf535da89e89ef2fadfd68baaae8e48fb18d7fb689f055428497ecd6576e99e6

Tx prefix hash: daa95484a443e5491e99181ecbb2fb063cd499cbc8b0a22e704b919a826fef25
Tx public key: 786e6283ff3d068da88435933d24edb32dc98aa1d4faa69019263650a03291ea
Timestamp: 1734964328 Timestamp [UCT]: 2024-12-23 14:32:08 Age [y:d:h:m:s]: 00:107:04:01:28
Block: 1181524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76354 RingCT/type: yes/0
Extra: 01786e6283ff3d068da88435933d24edb32dc98aa1d4faa69019263650a03291ea0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a21e33aba3b6d08bd352bb63a923e1251897aeced6fa2b6f1c553683f9e66bcd 0.600000000000 1667949 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": 1181534, "vin": [ { "gen": { "height": 1181524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a21e33aba3b6d08bd352bb63a923e1251897aeced6fa2b6f1c553683f9e66bcd" } } ], "extra": [ 1, 120, 110, 98, 131, 255, 61, 6, 141, 168, 132, 53, 147, 61, 36, 237, 179, 45, 201, 138, 161, 212, 250, 166, 144, 25, 38, 54, 80, 160, 50, 145, 234, 2, 17, 0, 0, 0, 4, 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