Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e975076a5824e947639c6968b992b26e0a0b468ce77c00d1187411eb3227ef7

Tx prefix hash: 77cfdcf4306db33ffaf326275a929d8a7c8526e7ffaabd4f51457b71ca92dac4
Tx public key: 83a8fdd5be2f4f8873f499c2bb1134ca2e26dac0c4c573e81da1141eb697ce32
Timestamp: 1733920443 Timestamp [UCT]: 2024-12-11 12:34:03 Age [y:d:h:m:s]: 00:185:18:00:13
Block: 1172863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132501 RingCT/type: yes/0
Extra: 0183a8fdd5be2f4f8873f499c2bb1134ca2e26dac0c4c573e81da1141eb697ce32021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d954c855c0b3a9e6c657265c5fd4ca77631955cb43986a812c34fb2b93a6eff 0.600000000000 1658810 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": 1172873, "vin": [ { "gen": { "height": 1172863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d954c855c0b3a9e6c657265c5fd4ca77631955cb43986a812c34fb2b93a6eff" } } ], "extra": [ 1, 131, 168, 253, 213, 190, 47, 79, 136, 115, 244, 153, 194, 187, 17, 52, 202, 46, 38, 218, 192, 196, 197, 115, 232, 29, 161, 20, 30, 182, 151, 206, 50, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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