Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42e35611f4d612d360dd3899d32576d2d1f09c324a795229a06f2a88721d501c

Tx prefix hash: 135c83dcffd020876f668ce8b1a3001a150b653f4b0424b66c4955da872ab249
Tx public key: 6d275030db14f24302244f01de6e9d7f3e65b62140a96d9f11a1a1608c9f4e31
Timestamp: 1730906975 Timestamp [UCT]: 2024-11-06 15:29:35 Age [y:d:h:m:s]: 00:155:01:01:53
Block: 1147894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110640 RingCT/type: yes/0
Extra: 016d275030db14f24302244f01de6e9d7f3e65b62140a96d9f11a1a1608c9f4e31021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 806328fa87234eac6ec04da2d2930e0c525f1fc47796aad49a5b865c23693a79 0.600000000000 1632607 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": 1147904, "vin": [ { "gen": { "height": 1147894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "806328fa87234eac6ec04da2d2930e0c525f1fc47796aad49a5b865c23693a79" } } ], "extra": [ 1, 109, 39, 80, 48, 219, 20, 242, 67, 2, 36, 79, 1, 222, 110, 157, 127, 62, 101, 182, 33, 64, 169, 109, 159, 17, 161, 161, 96, 140, 159, 78, 49, 2, 17, 0, 0, 0, 1, 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