Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c8c4d522171aabc13246f9d2df6effc0eeb2df8e5897be7b6b2540c95dd70ad

Tx prefix hash: b690e87e3cc548f90781b89147eaccad575e1d3511600438445058eeb4e476f9
Tx public key: ec33d87ad56fccfdb8bffd6a2029e50faa542d65adcb8312a9799f4039b6e1d0
Timestamp: 1703667171 Timestamp [UCT]: 2023-12-27 08:52:51 Age [y:d:h:m:s]: 01:355:23:56:15
Block: 922144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513312 RingCT/type: yes/0
Extra: 01ec33d87ad56fccfdb8bffd6a2029e50faa542d65adcb8312a9799f4039b6e1d002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a9fad00f1c318afdf333dbb3b660b76a7ee5e08fdc0fbe845f88475e0189e0a 0.600000000000 1379838 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": 922154, "vin": [ { "gen": { "height": 922144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a9fad00f1c318afdf333dbb3b660b76a7ee5e08fdc0fbe845f88475e0189e0a" } } ], "extra": [ 1, 236, 51, 216, 122, 213, 111, 204, 253, 184, 191, 253, 106, 32, 41, 229, 15, 170, 84, 45, 101, 173, 203, 131, 18, 169, 121, 159, 64, 57, 182, 225, 208, 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