Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 478aa4303addefb377d2b912b40ede601b7f1e0366f728befa6a9cd4421ce020

Tx prefix hash: 3bbce27856e064361a076ea124397ce3d2bfe58845220e69e6b2d3f36f789f1c
Tx public key: aabd4953679e9ce40675a1a59629f09fc59cdf5a79cd9746afe591aee1e6eede
Timestamp: 1726147609 Timestamp [UCT]: 2024-09-12 13:26:49 Age [y:d:h:m:s]: 00:202:23:42:12
Block: 1108514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144910 RingCT/type: yes/0
Extra: 01aabd4953679e9ce40675a1a59629f09fc59cdf5a79cd9746afe591aee1e6eede021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 365a401d7da6bacf91d94a01c7aff6ee7a5e80387aa30b5d4a0b140f0b53d708 0.600000000000 1586439 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": 1108524, "vin": [ { "gen": { "height": 1108514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "365a401d7da6bacf91d94a01c7aff6ee7a5e80387aa30b5d4a0b140f0b53d708" } } ], "extra": [ 1, 170, 189, 73, 83, 103, 158, 156, 228, 6, 117, 161, 165, 150, 41, 240, 159, 197, 156, 223, 90, 121, 205, 151, 70, 175, 229, 145, 174, 225, 230, 238, 222, 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