Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57855cbfe4aa6afbecbe0f6a9e908ab5a30be51371783af40eea098517282c86

Tx prefix hash: a943b3de60a7357ca34e3d1d83960693e3cc156f93be3c944f66a44c44255c82
Tx public key: 3e077809c6b1cba20fc394988a425875f69c828e2888ed3c7b25ccb8d454edc8
Timestamp: 1724030817 Timestamp [UCT]: 2024-08-19 01:26:57 Age [y:d:h:m:s]: 00:145:03:13:30
Block: 1090975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103817 RingCT/type: yes/0
Extra: 013e077809c6b1cba20fc394988a425875f69c828e2888ed3c7b25ccb8d454edc8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87d3b0154501879e617e818dbda8d59cca36909b072d66bb8a5f927ca1c40b6f 0.600000000000 1565600 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": 1090985, "vin": [ { "gen": { "height": 1090975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87d3b0154501879e617e818dbda8d59cca36909b072d66bb8a5f927ca1c40b6f" } } ], "extra": [ 1, 62, 7, 120, 9, 198, 177, 203, 162, 15, 195, 148, 152, 138, 66, 88, 117, 246, 156, 130, 142, 40, 136, 237, 60, 123, 37, 204, 184, 212, 84, 237, 200, 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