Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 714ece6950bac16c0c8a63baab0c0601744b5cfff1f4ee4c6b82ec34844c63da

Tx prefix hash: af81d0d2ccd06f388a5c837364c890dfce33727b4ada583751298d2ae9b76d61
Tx public key: c518234801f784015c24ebc5d650019e22cda28a148108c822fd16ae50c5d9ea
Timestamp: 1762339640 Timestamp [UCT]: 2025-11-05 10:47:20 Age [y:d:h:m:s]: 00:065:04:27:29
Block: 1405431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46694 RingCT/type: yes/0
Extra: 01c518234801f784015c24ebc5d650019e22cda28a148108c822fd16ae50c5d9ea0211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abd2baf004ae9daccdc5c72f78037ea882e6061a970f9ea1d5be24695cf3fae0 0.600000000000 1893802 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": 1405441, "vin": [ { "gen": { "height": 1405431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abd2baf004ae9daccdc5c72f78037ea882e6061a970f9ea1d5be24695cf3fae0" } } ], "extra": [ 1, 197, 24, 35, 72, 1, 247, 132, 1, 92, 36, 235, 197, 214, 80, 1, 158, 34, 205, 162, 138, 20, 129, 8, 200, 34, 253, 22, 174, 80, 197, 217, 234, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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