Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a28c1f4e5ae852eefea707cf52e142b57e846b64b20800c8c9dde4260b608c30

Tx prefix hash: f4b686f381777e828704c5fa64bf05c7ab8d45a0514b172645e633be1bb10deb
Tx public key: 323ec77b5d63da504def95eed5c047768f03f3f8f7483a6315420f0992f19588
Timestamp: 1773987089 Timestamp [UTC]: 2026-03-20 06:11:29 Age [y:d:h:m:s]: 00:240:02:06:25
Block: 1501724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177038 RingCT/type: yes/0
Extra: 01323ec77b5d63da504def95eed5c047768f03f3f8f7483a6315420f0992f19588021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cbfb2a95a2b60af24abe89bab5731020e6dbe0fb386c5541c63d815f0fbca1df 0.000600000000 1991410 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": 1501734, "vin": [ { "gen": { "height": 1501724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbfb2a95a2b60af24abe89bab5731020e6dbe0fb386c5541c63d815f0fbca1df" } } ], "extra": [ 1, 50, 62, 199, 123, 93, 99, 218, 80, 77, 239, 149, 238, 213, 192, 71, 118, 143, 3, 243, 248, 247, 72, 58, 99, 21, 66, 15, 9, 146, 241, 149, 136, 2, 17, 0, 0, 0, 1, 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: