Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa4e8ec9adf6bb1a058199ac37c007a14f2eb24daf650a9bfbfd84007ca8ee12

Tx prefix hash: 7d7d8db729cfcbcad16d0cab3f70f5ca445759aefc706d55d29619ba482ff6a1
Tx public key: ed9d7055c2fe2a21d522c624424e592c5d034d542fd3d69346f823ce5cbaae8b
Timestamp: 1761055552 Timestamp [UTC]: 2025-10-21 14:05:52 Age [y:d:h:m:s]: 01:027:01:53:30
Block: 1394822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285656 RingCT/type: yes/0
Extra: 01ed9d7055c2fe2a21d522c624424e592c5d034d542fd3d69346f823ce5cbaae8b021100000002df5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d4e5ebf2abcf4a3311295a235ac3666d131b5b04b62e666dbde2a140b989299c 0.000600000000 1883097 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": 1394832, "vin": [ { "gen": { "height": 1394822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4e5ebf2abcf4a3311295a235ac3666d131b5b04b62e666dbde2a140b989299c" } } ], "extra": [ 1, 237, 157, 112, 85, 194, 254, 42, 33, 213, 34, 198, 36, 66, 78, 89, 44, 93, 3, 77, 84, 47, 211, 214, 147, 70, 248, 35, 206, 92, 186, 174, 139, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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: