Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a2dfccda7b72f7149fd7c0ff787398fe8fe71973a56784ac6835b9c86df2da0

Tx prefix hash: bd88da10161695ee8a051ec7054f01d76af6ec5b88cbb66e16941f0c93abd0ce
Tx public key: 79097afd1f73ef3a4800d5f96f4e2ec413d7440a11d11764223bf58aa86b9a79
Timestamp: 1723021408 Timestamp [UCT]: 2024-08-07 09:03:28 Age [y:d:h:m:s]: 00:154:20:49:45
Block: 1082600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110799 RingCT/type: yes/0
Extra: 0179097afd1f73ef3a4800d5f96f4e2ec413d7440a11d11764223bf58aa86b9a7902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e578e2e37d3ca3ea82b14e3a3f45fa33f996afbff4489e0c49f507647c642e3 0.600000000000 1556429 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": 1082610, "vin": [ { "gen": { "height": 1082600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e578e2e37d3ca3ea82b14e3a3f45fa33f996afbff4489e0c49f507647c642e3" } } ], "extra": [ 1, 121, 9, 122, 253, 31, 115, 239, 58, 72, 0, 213, 249, 111, 78, 46, 196, 19, 215, 68, 10, 17, 209, 23, 100, 34, 59, 245, 138, 168, 107, 154, 121, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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