Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a64e4fa37ec917c46f7941f601276eb1e4be073af1fe1bd4def4d2f8d029444

Tx prefix hash: 81329d113ed0b4e686b9f784667845c792d0c75ff0d93bd12473ecfd1ab3896e
Tx public key: 605cb96caec200065e2ff2dd98f82b51f12900e664a2cccb1f5cf3c3fd5a84b4
Timestamp: 1685099479 Timestamp [UCT]: 2023-05-26 11:11:19 Age [y:d:h:m:s]: 01:278:04:45:50
Block: 768462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460012 RingCT/type: yes/0
Extra: 01605cb96caec200065e2ff2dd98f82b51f12900e664a2cccb1f5cf3c3fd5a84b402110000000133af99f4000000000000000000

1 output(s) for total of 1.744884024000 dcy

stealth address amount amount idx
00: 34af4a1072bf86e67b458d89c6585350fe671165155a20d990dfc74e0ae210d4 1.744884024000 1217663 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": 768472, "vin": [ { "gen": { "height": 768462 } } ], "vout": [ { "amount": 1744884024, "target": { "key": "34af4a1072bf86e67b458d89c6585350fe671165155a20d990dfc74e0ae210d4" } } ], "extra": [ 1, 96, 92, 185, 108, 174, 194, 0, 6, 94, 47, 242, 221, 152, 248, 43, 81, 241, 41, 0, 230, 100, 162, 204, 203, 31, 92, 243, 195, 253, 90, 132, 180, 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