Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d12f4935647671f12be083dad952cafd03f3d641af4b8813e7994210f26b126

Tx prefix hash: 46d48bf5e47afc31496014ea1baecf04069f2ce48af9a3fc2da2f8d95f1c822a
Tx public key: 579320b00f78ef432f3a0c8a162a989aef1d3d8cb7748a259728798b8816970b
Timestamp: 1737469940 Timestamp [UCT]: 2025-01-21 14:32:20 Age [y:d:h:m:s]: 00:148:04:11:30
Block: 1202200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105627 RingCT/type: yes/0
Extra: 01579320b00f78ef432f3a0c8a162a989aef1d3d8cb7748a259728798b8816970b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3edd1a3fe91a44e408b33edee1aa1e5e9c808b41c28fb486eb81e65918c89e57 0.600000000000 1688863 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": 1202210, "vin": [ { "gen": { "height": 1202200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3edd1a3fe91a44e408b33edee1aa1e5e9c808b41c28fb486eb81e65918c89e57" } } ], "extra": [ 1, 87, 147, 32, 176, 15, 120, 239, 67, 47, 58, 12, 138, 22, 42, 152, 154, 239, 29, 61, 140, 183, 116, 138, 37, 151, 40, 121, 139, 136, 22, 151, 11, 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