Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a8712b5940dccae2089b1a7862dd3173b7dafd8c8d7b24f3edfbc69708bb224

Tx prefix hash: ba97da1d900e5832752cedc3bcb37407293b9715c7e0c0cb6f69316be219583c
Tx public key: 53b0a99dec4c2953fb8b52e380d6266d9bf8eef22f6aa35ad052c509609346a0
Timestamp: 1658868637 Timestamp [UCT]: 2022-07-26 20:50:37 Age [y:d:h:m:s]: 02:293:22:30:18
Block: 552356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 731297 RingCT/type: yes/0
Extra: 0153b0a99dec4c2953fb8b52e380d6266d9bf8eef22f6aa35ad052c509609346a0021100000013ea8cbb85000000000000000000

1 output(s) for total of 9.074347510000 dcy

stealth address amount amount idx
00: 08f1af1d4f5a7c0d2d5d6b6a02fb5bac1fac18ce65fa35b66e7dd993893f297a 9.074347510000 984058 of 0

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": 552366, "vin": [ { "gen": { "height": 552356 } } ], "vout": [ { "amount": 9074347510, "target": { "key": "08f1af1d4f5a7c0d2d5d6b6a02fb5bac1fac18ce65fa35b66e7dd993893f297a" } } ], "extra": [ 1, 83, 176, 169, 157, 236, 76, 41, 83, 251, 139, 82, 227, 128, 214, 38, 109, 155, 248, 238, 242, 47, 106, 163, 90, 208, 82, 197, 9, 96, 147, 70, 160, 2, 17, 0, 0, 0, 19, 234, 140, 187, 133, 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