Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 634f9c1eee6a31a8aa60b384666c932e6ceb104a1e0f1317240494a783a81986

Tx prefix hash: 4b4adf05c275a04f9b499ca011282221531334f5555e494d901d43da28431ae7
Tx public key: 3e2a23e0f0cdb1d61de19b4e52d110acbeb2d77a06c9c01706e4098ce16805e4
Timestamp: 1738194283 Timestamp [UCT]: 2025-01-29 23:44:43 Age [y:d:h:m:s]: 00:043:12:53:26
Block: 1207974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31158 RingCT/type: yes/0
Extra: 013e2a23e0f0cdb1d61de19b4e52d110acbeb2d77a06c9c01706e4098ce16805e4021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57ef678a0eafd4bc88f02aec64105b58073d21b8898b732f935ba8c9a6ab2a1b 0.600000000000 1694701 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": 1207984, "vin": [ { "gen": { "height": 1207974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57ef678a0eafd4bc88f02aec64105b58073d21b8898b732f935ba8c9a6ab2a1b" } } ], "extra": [ 1, 62, 42, 35, 224, 240, 205, 177, 214, 29, 225, 155, 78, 82, 209, 16, 172, 190, 178, 215, 122, 6, 201, 192, 23, 6, 228, 9, 140, 225, 104, 5, 228, 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