Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5abf3e06a8192e0690387f676a583735a6cbebbcdbfcf307266725c197b00266

Tx prefix hash: 359407f5214f9d32f057e1db47e57454e40fdd41005ea89a567a59a9e8151042
Tx public key: e224060a602c27f291c06c46560d938e5d1d4b1966a4a9e539f1a03fe4730cb0
Timestamp: 1722209789 Timestamp [UCT]: 2024-07-28 23:36:29 Age [y:d:h:m:s]: 00:263:20:18:38
Block: 1075867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188496 RingCT/type: yes/0
Extra: 01e224060a602c27f291c06c46560d938e5d1d4b1966a4a9e539f1a03fe4730cb0021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca69900aafb48e72e11211d48a829392a34c62b255802152c79f4f53bb18a6a8 0.600000000000 1548398 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": 1075877, "vin": [ { "gen": { "height": 1075867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca69900aafb48e72e11211d48a829392a34c62b255802152c79f4f53bb18a6a8" } } ], "extra": [ 1, 226, 36, 6, 10, 96, 44, 39, 242, 145, 192, 108, 70, 86, 13, 147, 142, 93, 29, 75, 25, 102, 164, 169, 229, 57, 241, 160, 63, 228, 115, 12, 176, 2, 17, 0, 0, 0, 3, 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