Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06045f79423ece8ad6ce815005159ebb6c62ffd62a27fa7cfb9638c691249ddc

Tx prefix hash: f4823f5e094382ef8e9bcd1cb239c08ad41264f6fa11ece66c3d9654b0398543
Tx public key: 03cab06373305a8aaccc1b0e6b4ba4e8f0043793771e4b99b3b9b93d8efaba37
Timestamp: 1726869475 Timestamp [UCT]: 2024-09-20 21:57:55 Age [y:d:h:m:s]: 00:196:05:58:37
Block: 1114506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140070 RingCT/type: yes/0
Extra: 0103cab06373305a8aaccc1b0e6b4ba4e8f0043793771e4b99b3b9b93d8efaba37021100000001bdafe9cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f4befe7c120c00f728528aea7371c585d3b52694f8a1269f6f85afce1b56073 0.600000000000 1594307 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": 1114516, "vin": [ { "gen": { "height": 1114506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f4befe7c120c00f728528aea7371c585d3b52694f8a1269f6f85afce1b56073" } } ], "extra": [ 1, 3, 202, 176, 99, 115, 48, 90, 138, 172, 204, 27, 14, 107, 75, 164, 232, 240, 4, 55, 147, 119, 30, 75, 153, 179, 185, 185, 61, 142, 250, 186, 55, 2, 17, 0, 0, 0, 1, 189, 175, 233, 204, 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