Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dd1e7fa5929d002a511014e955ef67e57017564d92049a9a83c2ff06d724314

Tx prefix hash: 46dfa2eb2d38d4e782a78778336da9df221c15b416db861b1bcb9740b79fb4fd
Tx public key: e2a3508ab643c758d1a68a3be719554dbe6eeee1af3ef2ca3ad42ed25399d02a
Timestamp: 1725926816 Timestamp [UCT]: 2024-09-10 00:06:56 Age [y:d:h:m:s]: 00:279:02:46:35
Block: 1106701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199268 RingCT/type: yes/0
Extra: 01e2a3508ab643c758d1a68a3be719554dbe6eeee1af3ef2ca3ad42ed25399d02a021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0433ff8a587b713513fcf40233cd9bddc4c29c817e990f24ec625429b53b295 0.600000000000 1584302 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": 1106711, "vin": [ { "gen": { "height": 1106701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0433ff8a587b713513fcf40233cd9bddc4c29c817e990f24ec625429b53b295" } } ], "extra": [ 1, 226, 163, 80, 138, 182, 67, 199, 88, 209, 166, 138, 59, 231, 25, 85, 77, 190, 110, 238, 225, 175, 62, 242, 202, 58, 212, 46, 210, 83, 153, 208, 42, 2, 17, 0, 0, 0, 9, 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