Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80798eb722f39f7de438bc2bf62ab25df300bd15a9252bdd6fe183befde2e733

Tx prefix hash: ab164f40f81ed208f1c4388d9ee63311add8a2c5224892f274c16e8fd4408f28
Tx public key: 799e4f8458fa23e95d4faecefbd94a7e26cd9c4a03e54590503bc294e76aa6eb
Timestamp: 1773970992 Timestamp [UTC]: 2026-03-20 01:43:12 Age [y:d:h:m:s]: 00:240:14:13:53
Block: 1501593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177411 RingCT/type: yes/0
Extra: 01799e4f8458fa23e95d4faecefbd94a7e26cd9c4a03e54590503bc294e76aa6eb021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 068685893c84d28e254c92dc39977764055e4f4182c7b929fd9e889715b09b69 0.000600000000 1991277 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": 1501603, "vin": [ { "gen": { "height": 1501593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "068685893c84d28e254c92dc39977764055e4f4182c7b929fd9e889715b09b69" } } ], "extra": [ 1, 121, 158, 79, 132, 88, 250, 35, 233, 93, 79, 174, 206, 251, 217, 74, 126, 38, 205, 156, 74, 3, 229, 69, 144, 80, 59, 194, 148, 231, 106, 166, 235, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: