Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97048d48bff0adcee593368bd266112a262e4cd534d75556670500a003a0ad33

Tx prefix hash: 67f7deaed17cd0dfb1ae0e66b3e831fff6582137e2e9f603aa3f2a37e7a7404d
Tx public key: 466c8887ac4096a825d24c6f2b90ed13c03a393d9c05b37b3cb4799a0de715e0
Timestamp: 1730674169 Timestamp [UCT]: 2024-11-03 22:49:29 Age [y:d:h:m:s]: 00:197:12:39:28
Block: 1145962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141041 RingCT/type: yes/0
Extra: 01466c8887ac4096a825d24c6f2b90ed13c03a393d9c05b37b3cb4799a0de715e0021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d41d2ad16a6a0426487a9ba2ce43a3eff41aa7bcfd2977a733d71d1cb08db8d 0.600000000000 1630501 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": 1145972, "vin": [ { "gen": { "height": 1145962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d41d2ad16a6a0426487a9ba2ce43a3eff41aa7bcfd2977a733d71d1cb08db8d" } } ], "extra": [ 1, 70, 108, 136, 135, 172, 64, 150, 168, 37, 210, 76, 111, 43, 144, 237, 19, 192, 58, 57, 61, 156, 5, 179, 123, 60, 180, 121, 154, 13, 231, 21, 224, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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