Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7047d2a4a7d3be3586f08def181cabdc4bffd0b9fc809ee4c5d5228d6651c09c

Tx prefix hash: 0f9b0e9a90dd12d7fb7663733fa9398f5532d3a6b33b2283dec569d4cf38da37
Tx public key: 6a42c3b63ed76b612c88aed19082a314338609fa6c96c073607808671f22386d
Timestamp: 1702420979 Timestamp [UCT]: 2023-12-12 22:42:59 Age [y:d:h:m:s]: 01:037:07:09:47
Block: 911838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287997 RingCT/type: yes/0
Extra: 016a42c3b63ed76b612c88aed19082a314338609fa6c96c073607808671f22386d021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d30f3d5e501c383efc0eba35b0d51971096f21b4768070e44edc1159f35b1b9 0.600000000000 1369054 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": 911848, "vin": [ { "gen": { "height": 911838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d30f3d5e501c383efc0eba35b0d51971096f21b4768070e44edc1159f35b1b9" } } ], "extra": [ 1, 106, 66, 195, 182, 62, 215, 107, 97, 44, 136, 174, 209, 144, 130, 163, 20, 51, 134, 9, 250, 108, 150, 192, 115, 96, 120, 8, 103, 31, 34, 56, 109, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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