Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db06282ed0546b52f23c2e080971b8f79e54dbd20963a277fe008655e8d85a88

Tx prefix hash: 28eed246705182d19701758ebac19b19bd663d1f0a06878a58fa2a7a4a5b6075
Tx public key: 511328a4d4bab0f1d7742df66a4287bf77f8aa3fee2e4310c4d3220e03bbdec4
Timestamp: 1734141418 Timestamp [UCT]: 2024-12-14 01:56:58 Age [y:d:h:m:s]: 00:114:11:27:59
Block: 1174701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81586 RingCT/type: yes/0
Extra: 01511328a4d4bab0f1d7742df66a4287bf77f8aa3fee2e4310c4d3220e03bbdec40211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc7855458c9b6ff03a3eb30db994c82d21533786f4509bed938c850192aa4ce0 0.600000000000 1660888 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": 1174711, "vin": [ { "gen": { "height": 1174701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc7855458c9b6ff03a3eb30db994c82d21533786f4509bed938c850192aa4ce0" } } ], "extra": [ 1, 81, 19, 40, 164, 212, 186, 176, 241, 215, 116, 45, 246, 106, 66, 135, 191, 119, 248, 170, 63, 238, 46, 67, 16, 196, 211, 34, 14, 3, 187, 222, 196, 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