Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 704867631a65e4baa16db9db7be9cd7bc5cddcd4c7ec5e1977b5796f01fc8b02

Tx prefix hash: 3c88e2a18508d03dcb0dab630de17d6ea6e3bc48873e96a72b8248a45c4b189b
Tx public key: f554ede3064c1c3b044fba585525261f94b365554ec480970b7996c2f8ed67f1
Timestamp: 1774917515 Timestamp [UTC]: 2026-03-31 00:38:35 Age [y:d:h:m:s]: 00:231:19:09:36
Block: 1509434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171164 RingCT/type: yes/0
Extra: 01f554ede3064c1c3b044fba585525261f94b365554ec480970b7996c2f8ed67f1021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9a96a1c2e2763508c636cdb8ecb08e9c277b41107c52fc2a78a8b02bbbd00604 0.000600000000 1999208 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": 1509444, "vin": [ { "gen": { "height": 1509434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a96a1c2e2763508c636cdb8ecb08e9c277b41107c52fc2a78a8b02bbbd00604" } } ], "extra": [ 1, 245, 84, 237, 227, 6, 76, 28, 59, 4, 79, 186, 88, 85, 37, 38, 31, 148, 179, 101, 85, 78, 196, 128, 151, 11, 121, 150, 194, 248, 237, 103, 241, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: