Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 804fbee5416f28239db8424ad794773a711f7f9e55a7517d1e8a1c8d54d5faeb

Tx prefix hash: f2dd6c72cd457c5c8418d857467b8f8e197981bc4f99b7a215c1d74cc934ca29
Tx public key: c5fc915773499c8b10b3b393827f263c489b2ec13dd5b55a7effdf33786d1ce2
Timestamp: 1702424687 Timestamp [UTC]: 2023-12-12 23:44:47 Age [y:d:h:m:s]: 02:339:19:52:17
Block: 911868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 767996 RingCT/type: yes/0
Extra: 01c5fc915773499c8b10b3b393827f263c489b2ec13dd5b55a7effdf33786d1ce2021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8aa7f76720b17f1bdd9f4bc0bda137d63580c3fa1e0a1245c2da1ccb6158820e 0.000600000000 1369084 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 dinastycoin-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": 911878, "vin": [ { "gen": { "height": 911868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aa7f76720b17f1bdd9f4bc0bda137d63580c3fa1e0a1245c2da1ccb6158820e" } } ], "extra": [ 1, 197, 252, 145, 87, 115, 73, 156, 139, 16, 179, 179, 147, 130, 127, 38, 60, 72, 155, 46, 193, 61, 213, 181, 90, 126, 255, 223, 51, 120, 109, 28, 226, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: