Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4df035af7913854e0d232e13c07b60197c0b0b49ff946c7dd6c720bcdc8859f

Tx prefix hash: f6cc1ef655011d565c3397e0debc3350f32d60f474627ca09110250ed2c6dd9d
Tx public key: 48c6710aaf09abfff7d0d2aa3b0f24a0be9bb062634d304ff29ee3a989b3f3a0
Timestamp: 1718143862 Timestamp [UCT]: 2024-06-11 22:11:02 Age [y:d:h:m:s]: 00:337:10:40:42
Block: 1042170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241175 RingCT/type: yes/0
Extra: 0148c6710aaf09abfff7d0d2aa3b0f24a0be9bb062634d304ff29ee3a989b3f3a002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c0394272ff9be5f3901fdfdc132d890622cbb6c18ff49ce8cd32db2244bc231 0.600000000000 1511025 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": 1042180, "vin": [ { "gen": { "height": 1042170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c0394272ff9be5f3901fdfdc132d890622cbb6c18ff49ce8cd32db2244bc231" } } ], "extra": [ 1, 72, 198, 113, 10, 175, 9, 171, 255, 247, 208, 210, 170, 59, 15, 36, 160, 190, 155, 176, 98, 99, 77, 48, 79, 242, 158, 227, 169, 137, 179, 243, 160, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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