Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 823e75c1098d60d56f61c9fc62cf7e5a2ccb84f063cdb7842d184b0c11f20696

Tx prefix hash: 7dc94862baf5d62f74c499ac2575c568dfe830fff7074b3a4f05aa48ae23bda1
Tx public key: a492c42699e4bcf42890d037e69e5dcf2da9f8fc507fce4f8aeadef885dafac4
Timestamp: 1649365612 Timestamp [UCT]: 2022-04-07 21:06:52 Age [y:d:h:m:s]: 02:215:06:08:51
Block: 475374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 673586 RingCT/type: yes/0
Extra: 01a492c42699e4bcf42890d037e69e5dcf2da9f8fc507fce4f8aeadef885dafac4021100000007a272b9cb000000000000000000

1 output(s) for total of 16.326340222000 dcy

stealth address amount amount idx
00: 90dcbdaa7c46d4b6fdf8dd4dcdeb6c71b7efadb4153add898137ffbe65758f7e 16.326340222000 895607 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": 475384, "vin": [ { "gen": { "height": 475374 } } ], "vout": [ { "amount": 16326340222, "target": { "key": "90dcbdaa7c46d4b6fdf8dd4dcdeb6c71b7efadb4153add898137ffbe65758f7e" } } ], "extra": [ 1, 164, 146, 196, 38, 153, 228, 188, 244, 40, 144, 208, 55, 230, 158, 93, 207, 45, 169, 248, 252, 80, 127, 206, 79, 138, 234, 222, 248, 133, 218, 250, 196, 2, 17, 0, 0, 0, 7, 162, 114, 185, 203, 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