Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43c44fc2999936fb4544a19bf2c17617ce07daeac6d142c3b0fc4b957349ae66

Tx prefix hash: 2dac852ef23920c09de93e1806a67a85740c512ad51676684a9da1dd06c87b9f
Tx public key: c3924a4384793e58ea743a05a9817ba2bdc8ed887a11e10c18288c2d400d3e84
Timestamp: 1697340105 Timestamp [UCT]: 2023-10-15 03:21:45 Age [y:d:h:m:s]: 01:109:09:29:50
Block: 869889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339190 RingCT/type: yes/0
Extra: 01c3924a4384793e58ea743a05a9817ba2bdc8ed887a11e10c18288c2d400d3e8402110000000133af99f4000000000000000000

1 output(s) for total of 0.804816112000 dcy

stealth address amount amount idx
00: dd3649089ac6f38125e32ae5d410cebea923f4f0122f894c73f004fc8ca8625d 0.804816112000 1324754 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": 869899, "vin": [ { "gen": { "height": 869889 } } ], "vout": [ { "amount": 804816112, "target": { "key": "dd3649089ac6f38125e32ae5d410cebea923f4f0122f894c73f004fc8ca8625d" } } ], "extra": [ 1, 195, 146, 74, 67, 132, 121, 62, 88, 234, 116, 58, 5, 169, 129, 123, 162, 189, 200, 237, 136, 122, 17, 225, 12, 24, 40, 140, 45, 64, 13, 62, 132, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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