Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e96eea2783dee323f799f1442dff3d351d7336edb417d0e27186ecdf0a6c6aa

Tx prefix hash: 2fe614786922f603cb1675eacbcc4bb1f440385b0a82aaa9b259243fd8bda644
Tx public key: 18038d3478b643d3524af494f1d13def0a02bd3fdab5bd77a2fc1b7716480e06
Timestamp: 1681060670 Timestamp [UCT]: 2023-04-09 17:17:50 Age [y:d:h:m:s]: 01:320:20:51:48
Block: 734988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490557 RingCT/type: yes/0
Extra: 0118038d3478b643d3524af494f1d13def0a02bd3fdab5bd77a2fc1b7716480e06021100000001b3164c24000000000000000000

1 output(s) for total of 2.252578181000 dcy

stealth address amount amount idx
00: 00de0ad1a5e8b0aa2ffc35762c2ded40d05f3f2c981784bafbab988b47d0fde1 2.252578181000 1181265 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": 734998, "vin": [ { "gen": { "height": 734988 } } ], "vout": [ { "amount": 2252578181, "target": { "key": "00de0ad1a5e8b0aa2ffc35762c2ded40d05f3f2c981784bafbab988b47d0fde1" } } ], "extra": [ 1, 24, 3, 141, 52, 120, 182, 67, 211, 82, 74, 244, 148, 241, 209, 61, 239, 10, 2, 189, 63, 218, 181, 189, 119, 162, 252, 27, 119, 22, 72, 14, 6, 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