Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0251937c20abca3ce66b8c702c36590d65d79090e484f52c7649751019b15eb

Tx prefix hash: 4c596045f10c3d89468a417a43816f2f8bb420b2b29d632e0ac68ed41d70361d
Tx public key: 7a23875a3d25dfb928399be49538a7e1f6e47a4a31034a2304f4f805f64d251b
Timestamp: 1715830594 Timestamp [UCT]: 2024-05-16 03:36:34 Age [y:d:h:m:s]: 00:329:04:10:40
Block: 1022996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235279 RingCT/type: yes/0
Extra: 017a23875a3d25dfb928399be49538a7e1f6e47a4a31034a2304f4f805f64d251b0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0f1b3a1f0887c6bc21df50c0fdb933635c5802828559b93ec60ebad3f82581d 0.600000000000 1487759 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": 1023006, "vin": [ { "gen": { "height": 1022996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f1b3a1f0887c6bc21df50c0fdb933635c5802828559b93ec60ebad3f82581d" } } ], "extra": [ 1, 122, 35, 135, 90, 61, 37, 223, 185, 40, 57, 155, 228, 149, 56, 167, 225, 246, 228, 122, 74, 49, 3, 74, 35, 4, 244, 248, 5, 246, 77, 37, 27, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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