Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afc5736428d6675de8ee8633c19a3eca0a7ccdc84d797e181af4215182048316

Tx prefix hash: 1430fa355130fc5342e3f5ca5860c63b6c98f31103be7d805e13d787a33aa938
Tx public key: c197d48dc786ee882c5da184da7cd418052905f8ff986a98a875ee60ccdf076a
Timestamp: 1730330577 Timestamp [UCT]: 2024-10-30 23:22:57 Age [y:d:h:m:s]: 00:028:11:14:33
Block: 1143116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20380 RingCT/type: yes/0
Extra: 01c197d48dc786ee882c5da184da7cd418052905f8ff986a98a875ee60ccdf076a021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4675d897f982e6b92533b66ccd0ad04c7f1e0bc419e6e0e314cae1ff2f6b81ea 0.600000000000 1626979 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": 1143126, "vin": [ { "gen": { "height": 1143116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4675d897f982e6b92533b66ccd0ad04c7f1e0bc419e6e0e314cae1ff2f6b81ea" } } ], "extra": [ 1, 193, 151, 212, 141, 199, 134, 238, 136, 44, 93, 161, 132, 218, 124, 212, 24, 5, 41, 5, 248, 255, 152, 106, 152, 168, 117, 238, 96, 204, 223, 7, 106, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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