Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46375c451e2ed2aa0e1a9191e2b4f9cc984474d8554d73742c392c2956aefa15

Tx prefix hash: cd7a557816991004dca3504017b11c4434c7b19074a869b083088a78f0125a64
Tx public key: e52c701c073a6bbb4c53c6a8cb38792b4cd16bd851caa75e2c9595bcd4911f69
Timestamp: 1704961350 Timestamp [UCT]: 2024-01-11 08:22:30 Age [y:d:h:m:s]: 01:085:08:33:48
Block: 932862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322106 RingCT/type: yes/0
Extra: 01e52c701c073a6bbb4c53c6a8cb38792b4cd16bd851caa75e2c9595bcd4911f6902110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d34c7c26a7388cddee438239960edbf546aca9c9a7937e3b227425a83c69c66 0.600000000000 1390802 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": 932872, "vin": [ { "gen": { "height": 932862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d34c7c26a7388cddee438239960edbf546aca9c9a7937e3b227425a83c69c66" } } ], "extra": [ 1, 229, 44, 112, 28, 7, 58, 107, 187, 76, 83, 198, 168, 203, 56, 121, 43, 76, 209, 107, 216, 81, 202, 167, 94, 44, 149, 149, 188, 212, 145, 31, 105, 2, 17, 0, 0, 0, 8, 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