Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb7738db34ff8049bca9292bfd2968f15cef52ba5c0b9f06e805cc5a8259ee4c

Tx prefix hash: 3bfb7e4ec283c92436e5f3533f9cd3f9498c0509007136c1fae0df0bfe980753
Tx public key: 2ebe9aa73ae6384fc7bbbd63b3250a22d546d5aaf4e8086c0e35a247b6e87f6c
Timestamp: 1742556620 Timestamp [UTC]: 2025-03-21 11:30:20 Age [y:d:h:m:s]: 01:244:07:37:32
Block: 1244108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438771 RingCT/type: yes/0
Extra: 012ebe9aa73ae6384fc7bbbd63b3250a22d546d5aaf4e8086c0e35a247b6e87f6c02110000000658cb2e2b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e2a0dc221706de9efe484b13b369c9eee19baf0c626922d8080d9f0e9ea8c2a2 0.000600000000 1731099 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": 1244118, "vin": [ { "gen": { "height": 1244108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2a0dc221706de9efe484b13b369c9eee19baf0c626922d8080d9f0e9ea8c2a2" } } ], "extra": [ 1, 46, 190, 154, 167, 58, 230, 56, 79, 199, 187, 189, 99, 179, 37, 10, 34, 213, 70, 213, 170, 244, 232, 8, 108, 14, 53, 162, 71, 182, 232, 127, 108, 2, 17, 0, 0, 0, 6, 88, 203, 46, 43, 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: