Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dac8259db15000f053dce8746cb95d8083976c9058d9b6e893f6f604f857354

Tx prefix hash: 293c6b5ee7d389ca88ee0bf8e87fd11fc754187b89d0c0ff6902dd1085984097
Tx public key: 7706245a6df5cfdee750b9b564401442a0779d5a60e80d61c5eb2ee60371d635
Timestamp: 1687056702 Timestamp [UCT]: 2023-06-18 02:51:42 Age [y:d:h:m:s]: 01:209:06:57:17
Block: 784682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410977 RingCT/type: yes/0
Extra: 017706245a6df5cfdee750b9b564401442a0779d5a60e80d61c5eb2ee60371d63502110000000275e3f0e9000000000000000000

1 output(s) for total of 1.541781923000 dcy

stealth address amount amount idx
00: d7c1e65ef54a1c5a4e1d78357976aaa831494b994546e0891f7b78f0fc5a7cc6 1.541781923000 1234581 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": 784692, "vin": [ { "gen": { "height": 784682 } } ], "vout": [ { "amount": 1541781923, "target": { "key": "d7c1e65ef54a1c5a4e1d78357976aaa831494b994546e0891f7b78f0fc5a7cc6" } } ], "extra": [ 1, 119, 6, 36, 90, 109, 245, 207, 222, 231, 80, 185, 181, 100, 64, 20, 66, 160, 119, 157, 90, 96, 232, 13, 97, 197, 235, 46, 230, 3, 113, 214, 53, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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