Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0843924475be98c4f45fd92da75edc52c420b2df208adab0063b97d4dad877ad

Tx prefix hash: 16dd54e8ca933238ead5e8e23b2a9fd4c146e9178ef70e2eef0a5d6a045f1919
Tx public key: 0b5e3478fe22c9cc69e8fdcaa167671b0a1476be80c4e610db36e77172c4de81
Timestamp: 1719370389 Timestamp [UCT]: 2024-06-26 02:53:09 Age [y:d:h:m:s]: 00:278:18:17:44
Block: 1052321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199197 RingCT/type: yes/0
Extra: 010b5e3478fe22c9cc69e8fdcaa167671b0a1476be80c4e610db36e77172c4de810211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2659b55fa5a458cfbec5003535b8a78ad802cc8ac330c11aeebe88d100b5efc0 0.600000000000 1522644 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": 1052331, "vin": [ { "gen": { "height": 1052321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2659b55fa5a458cfbec5003535b8a78ad802cc8ac330c11aeebe88d100b5efc0" } } ], "extra": [ 1, 11, 94, 52, 120, 254, 34, 201, 204, 105, 232, 253, 202, 161, 103, 103, 27, 10, 20, 118, 190, 128, 196, 230, 16, 219, 54, 231, 113, 114, 196, 222, 129, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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