Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aded8a457ee702b3b8b89f0609122b03a7dc384790be836cab61cfc632c34d4d

Tx prefix hash: 612cc987906f089044f313df39e1c5d3f9f55c7deb388f2e23ebb67294123fc5
Tx public key: 40d41e68bd0d60de7c454d0c0d1066368a0da2ad278099112e7ec83d561846b0
Timestamp: 1724739050 Timestamp [UCT]: 2024-08-27 06:10:50 Age [y:d:h:m:s]: 00:226:02:17:24
Block: 1096832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161462 RingCT/type: yes/0
Extra: 0140d41e68bd0d60de7c454d0c0d1066368a0da2ad278099112e7ec83d561846b0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc10f1d43d982915f0b99b0d5020c03c60f42cbce54ad2b290d9b54a8f4af2ef 0.600000000000 1572027 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": 1096842, "vin": [ { "gen": { "height": 1096832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc10f1d43d982915f0b99b0d5020c03c60f42cbce54ad2b290d9b54a8f4af2ef" } } ], "extra": [ 1, 64, 212, 30, 104, 189, 13, 96, 222, 124, 69, 77, 12, 13, 16, 102, 54, 138, 13, 162, 173, 39, 128, 153, 17, 46, 126, 200, 61, 86, 24, 70, 176, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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