Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 869b531e07e55c0b7b0f5b7be215c7fc21cfdf44200cb41e901fb12a752a4f27

Tx prefix hash: 192fe3911c780033374dbe6871fd17e5392b48389325812ebf5175f94671c36c
Tx public key: 2bcabaee5f23973f82dfc038d9fa83fd00f3f2ff1ae34cfa4610020238e5c45e
Timestamp: 1707642447 Timestamp [UCT]: 2024-02-11 09:07:27 Age [y:d:h:m:s]: 01:091:06:14:48
Block: 955094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326291 RingCT/type: yes/0
Extra: 012bcabaee5f23973f82dfc038d9fa83fd00f3f2ff1ae34cfa4610020238e5c45e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dc9e057cbf051e9c9dab41af99ad117b54d4f86a9f38a8686a5433647f5bdec 0.600000000000 1414376 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": 955104, "vin": [ { "gen": { "height": 955094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dc9e057cbf051e9c9dab41af99ad117b54d4f86a9f38a8686a5433647f5bdec" } } ], "extra": [ 1, 43, 202, 186, 238, 95, 35, 151, 63, 130, 223, 192, 56, 217, 250, 131, 253, 0, 243, 242, 255, 26, 227, 76, 250, 70, 16, 2, 2, 56, 229, 196, 94, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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