Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0befc822c0c322cf690ff1c58c0d6a82089862036d52b220efb557b7cdbf52ef

Tx prefix hash: 38f7911fc8725b8e83d2042f66667cd50f30ebcd81783a4af26fd570e3db5e71
Tx public key: 786569772a86821b8bdf99563f7306bae4f8b6d4f7561f3d00fff6af69634f04
Timestamp: 1774809589 Timestamp [UTC]: 2026-03-29 18:39:49 Age [y:d:h:m:s]: 00:234:02:37:34
Block: 1508551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172840 RingCT/type: yes/0
Extra: 01786569772a86821b8bdf99563f7306bae4f8b6d4f7561f3d00fff6af69634f04021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4287037d0e1738642df5dd3d2f7a71d1beb293d553ed8ef06805d6fa13c9e9b5 0.000600000000 1998303 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": 1508561, "vin": [ { "gen": { "height": 1508551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4287037d0e1738642df5dd3d2f7a71d1beb293d553ed8ef06805d6fa13c9e9b5" } } ], "extra": [ 1, 120, 101, 105, 119, 42, 134, 130, 27, 139, 223, 153, 86, 63, 115, 6, 186, 228, 248, 182, 212, 247, 86, 31, 61, 0, 255, 246, 175, 105, 99, 79, 4, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: