Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73c165f9eb38515aca4e1d6fad0353a0dcec864ffe157e3704b0e3f8c2920080

Tx prefix hash: 7ea2ed0058210195167b77dde9800bb7154c6c9e68c6d938916a43e129d06027
Tx public key: 1d3f21f6f60b566e1beaa2aea5f45912e91785b86526c9a0bac379eaca1a2ab8
Timestamp: 1706533086 Timestamp [UCT]: 2024-01-29 12:58:06 Age [y:d:h:m:s]: 01:053:20:40:29
Block: 945886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299574 RingCT/type: yes/0
Extra: 011d3f21f6f60b566e1beaa2aea5f45912e91785b86526c9a0bac379eaca1a2ab802110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e32101507a501e1505885d0c6b1da057c43e878e8eece4108dd700e39d5d5b42 0.600000000000 1404210 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": 945896, "vin": [ { "gen": { "height": 945886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e32101507a501e1505885d0c6b1da057c43e878e8eece4108dd700e39d5d5b42" } } ], "extra": [ 1, 29, 63, 33, 246, 246, 11, 86, 110, 27, 234, 162, 174, 165, 244, 89, 18, 233, 23, 133, 184, 101, 38, 201, 160, 186, 195, 121, 234, 202, 26, 42, 184, 2, 17, 0, 0, 0, 16, 89, 218, 211, 245, 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