Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fc5a9f67cf530c2b1e4cabc8c41c483a5d096e5a27426c5caa8389bc5983a22

Tx prefix hash: 21803be21efa205d658374f5fa1e036eaf5d7582eb8217b4c91d50c47647fecf
Tx public key: 8a2ab4c6a54941b16baa25d8ceb0de3cf23e7d9767305bb8e67e6a781b6fe929
Timestamp: 1739805787 Timestamp [UCT]: 2025-02-17 15:23:07 Age [y:d:h:m:s]: 00:276:17:24:38
Block: 1221289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195539 RingCT/type: yes/0
Extra: 018a2ab4c6a54941b16baa25d8ceb0de3cf23e7d9767305bb8e67e6a781b6fe9290211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba0ff678191db581e71eeffb59e1391f4f615e7f4bc127ac18f061990684e051 0.600000000000 1708134 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": 1221299, "vin": [ { "gen": { "height": 1221289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba0ff678191db581e71eeffb59e1391f4f615e7f4bc127ac18f061990684e051" } } ], "extra": [ 1, 138, 42, 180, 198, 165, 73, 65, 177, 107, 170, 37, 216, 206, 176, 222, 60, 242, 62, 125, 151, 103, 48, 91, 184, 230, 126, 106, 120, 27, 111, 233, 41, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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