Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eff09b8750f917e4a911e8af07e9a711b93bf3fe1f5f6e17586f848b41a12bc8

Tx prefix hash: 9b9743ecd32f14500bafc8a1f85efb5934826d6fb5d06d7f7997da5fb977920a
Tx public key: 6754230a83cfc11f7f0e459a48163be2a5f5aac6cae7f905fa2496211b42ebdd
Timestamp: 1734194402 Timestamp [UCT]: 2024-12-14 16:40:02 Age [y:d:h:m:s]: 00:099:02:03:52
Block: 1175141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70589 RingCT/type: yes/0
Extra: 016754230a83cfc11f7f0e459a48163be2a5f5aac6cae7f905fa2496211b42ebdd021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92a09fb95a03046380b3eed70642176b274e1ecba3955be8440a4cf38b3c82a2 0.600000000000 1661380 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": 1175151, "vin": [ { "gen": { "height": 1175141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92a09fb95a03046380b3eed70642176b274e1ecba3955be8440a4cf38b3c82a2" } } ], "extra": [ 1, 103, 84, 35, 10, 131, 207, 193, 31, 127, 14, 69, 154, 72, 22, 59, 226, 165, 245, 170, 198, 202, 231, 249, 5, 250, 36, 150, 33, 27, 66, 235, 221, 2, 17, 0, 0, 0, 7, 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