Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84f742b9bd6bddfc3ec54f992229e3558925bea05a3fcd594da929cfe053c133

Tx prefix hash: 117800ea48d2a0c9f5d9ee1b23116de210c7a3dd621974df7548a3660b38ace6
Tx public key: 79aac6d3e219f0926df5da0fca9dd77f8bed5421f3e654781ccd93273f222c5c
Timestamp: 1731034425 Timestamp [UCT]: 2024-11-08 02:53:45 Age [y:d:h:m:s]: 00:153:05:38:59
Block: 1148954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109343 RingCT/type: yes/0
Extra: 0179aac6d3e219f0926df5da0fca9dd77f8bed5421f3e654781ccd93273f222c5c0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea477a14f3d5f13745629244308c5feca7d5962ba88e4016b566e8b047e873e3 0.600000000000 1633925 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": 1148964, "vin": [ { "gen": { "height": 1148954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea477a14f3d5f13745629244308c5feca7d5962ba88e4016b566e8b047e873e3" } } ], "extra": [ 1, 121, 170, 198, 211, 226, 25, 240, 146, 109, 245, 218, 15, 202, 157, 215, 127, 139, 237, 84, 33, 243, 230, 84, 120, 28, 205, 147, 39, 63, 34, 44, 92, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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