Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4328af2c362b77fc3225c2434559952e951a3eea3f9994991ab99fc660fce169

Tx prefix hash: f8a4648b042164bdc72e05f3cbc08fb608bb482ba38683284003cc7a1a528add
Tx public key: 57c8b99529910bceea72b2c81c8ad74261a55d6b70cd6da0e245c0c21630d2a7
Timestamp: 1711412963 Timestamp [UCT]: 2024-03-26 00:29:23 Age [y:d:h:m:s]: 01:196:19:28:45
Block: 986385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399280 RingCT/type: yes/0
Extra: 0157c8b99529910bceea72b2c81c8ad74261a55d6b70cd6da0e245c0c21630d2a702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ce1aaf618d64deccefc2cd1fe50ef8ff2be50e234bdedd66c66a96ca08458cd 0.600000000000 1446614 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": 986395, "vin": [ { "gen": { "height": 986385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ce1aaf618d64deccefc2cd1fe50ef8ff2be50e234bdedd66c66a96ca08458cd" } } ], "extra": [ 1, 87, 200, 185, 149, 41, 145, 11, 206, 234, 114, 178, 200, 28, 138, 215, 66, 97, 165, 93, 107, 112, 205, 109, 160, 226, 69, 192, 194, 22, 48, 210, 167, 2, 17, 0, 0, 0, 2, 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