Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9966939df06fdf6f33659ffbf63f8b0e46ce38f3940bc327bc041e554e840f30

Tx prefix hash: bda357147b3690d977429e10f8505f4039489396847ff6cc8dd7f0f5e12403c7
Tx public key: 371d93f594c52b8edb61088afb579128bb4c4c5401753afb49a16e71c386d8c6
Timestamp: 1695602745 Timestamp [UCT]: 2023-09-25 00:45:45 Age [y:d:h:m:s]: 01:152:21:39:17
Block: 855490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370311 RingCT/type: yes/0
Extra: 01371d93f594c52b8edb61088afb579128bb4c4c5401753afb49a16e71c386d8c602110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.898269281000 dcy

stealth address amount amount idx
00: ef9c4f539b68e87480d08e3904fa50fb3734e82f64ad3ab947029006ff5892d7 0.898269281000 1309514 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": 855500, "vin": [ { "gen": { "height": 855490 } } ], "vout": [ { "amount": 898269281, "target": { "key": "ef9c4f539b68e87480d08e3904fa50fb3734e82f64ad3ab947029006ff5892d7" } } ], "extra": [ 1, 55, 29, 147, 245, 148, 197, 43, 142, 219, 97, 8, 138, 251, 87, 145, 40, 187, 76, 76, 84, 1, 117, 58, 251, 73, 161, 110, 113, 195, 134, 216, 198, 2, 17, 0, 0, 0, 11, 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