Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f02ad13bb5538695619e755c22f957417b526e49b85d5b095dfdaac02fd23bf

Tx prefix hash: 67a949226891cf135c39b5c2d89e946af89b1c2801e296bd1018fa2316f64b69
Tx public key: b5fff6d2874a614e2f257ee9b4de70dfdcfdb348c8a3cd3e43cd4248db41c9ba
Timestamp: 1723834734 Timestamp [UCT]: 2024-08-16 18:58:54 Age [y:d:h:m:s]: 00:297:23:58:10
Block: 1089349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212900 RingCT/type: yes/0
Extra: 01b5fff6d2874a614e2f257ee9b4de70dfdcfdb348c8a3cd3e43cd4248db41c9ba021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b71d284b25d4b837a4f2c5a553bf66957fcabc1d22c8061b5428bba67b33cf53 0.600000000000 1563968 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": 1089359, "vin": [ { "gen": { "height": 1089349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b71d284b25d4b837a4f2c5a553bf66957fcabc1d22c8061b5428bba67b33cf53" } } ], "extra": [ 1, 181, 255, 246, 210, 135, 74, 97, 78, 47, 37, 126, 233, 180, 222, 112, 223, 220, 253, 179, 72, 200, 163, 205, 62, 67, 205, 66, 72, 219, 65, 201, 186, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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