Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56ff7b58fc5ebfd82f159158e5aca5b89b8255f0dbab97da31c138937003c5bf

Tx prefix hash: b40fcdb725992bb8c0f41e141c94a89a164d01f6e0d41e175b09d97f39781c24
Tx public key: 1fa9cfaf6b75888acf65f4c75974720e6e6dc88f4a53e0404770ff0a7cb0690d
Timestamp: 1681346673 Timestamp [UCT]: 2023-04-13 00:44:33 Age [y:d:h:m:s]: 02:041:11:29:58
Block: 737333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551844 RingCT/type: yes/0
Extra: 011fa9cfaf6b75888acf65f4c75974720e6e6dc88f4a53e0404770ff0a7cb0690d021100000001b3164c24000000000000000000

1 output(s) for total of 2.212695679000 dcy

stealth address amount amount idx
00: 1fd8a4bc323bf858d38983c8058ab767e52012830364aaf911d9ba1196e196b7 2.212695679000 1183876 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": 737343, "vin": [ { "gen": { "height": 737333 } } ], "vout": [ { "amount": 2212695679, "target": { "key": "1fd8a4bc323bf858d38983c8058ab767e52012830364aaf911d9ba1196e196b7" } } ], "extra": [ 1, 31, 169, 207, 175, 107, 117, 136, 138, 207, 101, 244, 199, 89, 116, 114, 14, 110, 109, 200, 143, 74, 83, 224, 64, 71, 112, 255, 10, 124, 176, 105, 13, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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