Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f306f4e20da3a32c4160b87156c6c18994f435efa35fc0d849849ff0abe2e19

Tx prefix hash: 9e54f97b6fcf3f355792fee9718aa26e5b793f4a3af41f97acb164bf1837ec2d
Tx public key: cf2a91a2f94ca8eebdb926aa3b4f3d02976d95420594626862f79d9db518937c
Timestamp: 1774367782 Timestamp [UTC]: 2026-03-24 15:56:22 Age [y:d:h:m:s]: 00:237:08:36:09
Block: 1504882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175138 RingCT/type: yes/0
Extra: 01cf2a91a2f94ca8eebdb926aa3b4f3d02976d95420594626862f79d9db518937c021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 492877a7edb7c0ce82354bdc8b9910cc430331fb67f6edf47c0d48113c68a48e 0.000600000000 1994610 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": 1504892, "vin": [ { "gen": { "height": 1504882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "492877a7edb7c0ce82354bdc8b9910cc430331fb67f6edf47c0d48113c68a48e" } } ], "extra": [ 1, 207, 42, 145, 162, 249, 76, 168, 238, 189, 185, 38, 170, 59, 79, 61, 2, 151, 109, 149, 66, 5, 148, 98, 104, 98, 247, 157, 157, 181, 24, 147, 124, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: