Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57493dd749ad5af347ebdb9eddca54b59c98ae998fe1dac01cc0bf2f16df22a9

Tx prefix hash: aec78f51b5302921b97f2608afdab5c15cd16eb4238665b9d712b5af79d22ca2
Tx public key: d3c9492839189fd8b277c4ddfbe81c194e5dad4503942a8b1d5d0c7c315cf0a7
Timestamp: 1751953841 Timestamp [UTC]: 2025-07-08 05:50:41 Age [y:d:h:m:s]: 01:133:03:01:57
Block: 1321112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359904 RingCT/type: yes/0
Extra: 01d3c9492839189fd8b277c4ddfbe81c194e5dad4503942a8b1d5d0c7c315cf0a70211000000072609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0ae7abbd75431014dbd9c8003a1cf24710c44380a4856eb735f2b56d924ce69b 0.000600000000 1808815 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": 1321122, "vin": [ { "gen": { "height": 1321112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ae7abbd75431014dbd9c8003a1cf24710c44380a4856eb735f2b56d924ce69b" } } ], "extra": [ 1, 211, 201, 73, 40, 57, 24, 159, 216, 178, 119, 196, 221, 251, 232, 28, 25, 78, 93, 173, 69, 3, 148, 42, 139, 29, 93, 12, 124, 49, 92, 240, 167, 2, 17, 0, 0, 0, 7, 38, 9, 179, 160, 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: