Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67e3ad6bb730ad5046f9b8e3e46814c8572cd4e0b762536a984244eaeb8c9868

Tx prefix hash: 16ee53f13cb59f9a3ab60da90a676aa2d6080bfe7c5412f4bd111465cbd25c27
Tx public key: 4c0dd14d26b5a4d020ad724c913ed9e800caf3cbd43d1775f32723115fccaeeb
Timestamp: 1729885026 Timestamp [UCT]: 2024-10-25 19:37:06 Age [y:d:h:m:s]: 00:147:03:53:41
Block: 1139469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104970 RingCT/type: yes/0
Extra: 014c0dd14d26b5a4d020ad724c913ed9e800caf3cbd43d1775f32723115fccaeeb021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f3c8ab90615425ed81843b8b1f2b4ecb8c9268fb519d17bcf426f44ad1fde0d 0.600000000000 1623256 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": 1139479, "vin": [ { "gen": { "height": 1139469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f3c8ab90615425ed81843b8b1f2b4ecb8c9268fb519d17bcf426f44ad1fde0d" } } ], "extra": [ 1, 76, 13, 209, 77, 38, 181, 164, 208, 32, 173, 114, 76, 145, 62, 217, 232, 0, 202, 243, 203, 212, 61, 23, 117, 243, 39, 35, 17, 95, 204, 174, 235, 2, 17, 0, 0, 0, 1, 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