Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a41aae3560fb6002d87cb800c3b27bd77d430ff4a6b0f2781958f8b040166b50

Tx prefix hash: 74f3f25c69b54f41f67f643ce069e480836a23f94f5fc438e3f28350be5a7b3f
Tx public key: ec446409edee9a3209f45a8bbdeed6f1139ce93c29d29a18e19119e33b6b5aa9
Timestamp: 1686249664 Timestamp [UCT]: 2023-06-08 18:41:04 Age [y:d:h:m:s]: 02:198:04:04:51
Block: 778006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 661447 RingCT/type: yes/0
Extra: 01ec446409edee9a3209f45a8bbdeed6f1139ce93c29d29a18e19119e33b6b5aa9021100000001faf35c9c000000000000000000

1 output(s) for total of 1.622345388000 dcy

stealth address amount amount idx
00: 830e912995ab533063778ac72f546bee8f66761c156376dcae03483b31b5fd25 1.622345388000 1227621 of 0

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": 778016, "vin": [ { "gen": { "height": 778006 } } ], "vout": [ { "amount": 1622345388, "target": { "key": "830e912995ab533063778ac72f546bee8f66761c156376dcae03483b31b5fd25" } } ], "extra": [ 1, 236, 68, 100, 9, 237, 238, 154, 50, 9, 244, 90, 139, 189, 238, 214, 241, 19, 156, 233, 60, 41, 210, 154, 24, 225, 145, 25, 227, 59, 107, 90, 169, 2, 17, 0, 0, 0, 1, 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