Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c05575f2dd1c7f6313478a8870fdec02fdf1628606824ad53f6cad46bab88bc9

Tx prefix hash: 9bb49cc0b37a1ae0be9a6ca286dde9dc831e957a3396d619edace7263bbeae55
Tx public key: 3b58627095fef44232c13eab85dee28620e295833261a373c0cbd4a6f0edab58
Timestamp: 1706558584 Timestamp [UCT]: 2024-01-29 20:03:04 Age [y:d:h:m:s]: 01:287:18:53:34
Block: 946101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464487 RingCT/type: yes/0
Extra: 013b58627095fef44232c13eab85dee28620e295833261a373c0cbd4a6f0edab5802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e158ca0dddf0c8d2968a47ac3c267b5ee625e66bd396f4e8aea31d9b6a8f1b47 0.600000000000 1404431 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": 946111, "vin": [ { "gen": { "height": 946101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e158ca0dddf0c8d2968a47ac3c267b5ee625e66bd396f4e8aea31d9b6a8f1b47" } } ], "extra": [ 1, 59, 88, 98, 112, 149, 254, 244, 66, 50, 193, 62, 171, 133, 222, 226, 134, 32, 226, 149, 131, 50, 97, 163, 115, 192, 203, 212, 166, 240, 237, 171, 88, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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