Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf4ed7230a4fa9259a95b2d72c8a807101a7659db2a1028eb0b073a8dc6c1ea7

Tx prefix hash: 8fa7fc0ea4b7a3d87705f07bb8f3c67a47db28ac4561f82260be3ccadfde8a06
Tx public key: a68dbe158397474d7a4702cd7ada257cc05febd53022a655a1860bc908ddcff6
Timestamp: 1757928707 Timestamp [UTC]: 2025-09-15 09:31:47 Age [y:d:h:m:s]: 01:063:22:50:18
Block: 1368894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312107 RingCT/type: yes/0
Extra: 01a68dbe158397474d7a4702cd7ada257cc05febd53022a655a1860bc908ddcff6021100000006b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd84712d704d6d5a5f26b2e77b72f2ca23b42baa688bbddaebc0faf8d4a3e5c3 0.000600000000 1856945 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": 1368904, "vin": [ { "gen": { "height": 1368894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd84712d704d6d5a5f26b2e77b72f2ca23b42baa688bbddaebc0faf8d4a3e5c3" } } ], "extra": [ 1, 166, 141, 190, 21, 131, 151, 71, 77, 122, 71, 2, 205, 122, 218, 37, 124, 192, 95, 235, 213, 48, 34, 166, 85, 161, 134, 11, 201, 8, 221, 207, 246, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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: