Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ffb7c3e4d67cd0378991e7d84f80665d38de2b2a2d18a4e9c3ce21c15b21e57

Tx prefix hash: c908fa2c6bcd65b4e4a2d276075b0aee90bbc22b961e69cab4990cf48c14c431
Tx public key: 95ae50ec152b0cadc915489a5a45819818f12a1fe8482c8b3aded4f91ee4b87b
Timestamp: 1749281756 Timestamp [UTC]: 2025-06-07 07:35:56 Age [y:d:h:m:s]: 01:161:09:37:06
Block: 1299769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379273 RingCT/type: yes/0
Extra: 0195ae50ec152b0cadc915489a5a45819818f12a1fe8482c8b3aded4f91ee4b87b02110000000443846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b2d8f9a253dd8e459d418e28a449e69e6ba508e447c5297c64f790442f02d5c0 0.000600000000 1787308 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": 1299779, "vin": [ { "gen": { "height": 1299769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2d8f9a253dd8e459d418e28a449e69e6ba508e447c5297c64f790442f02d5c0" } } ], "extra": [ 1, 149, 174, 80, 236, 21, 43, 12, 173, 201, 21, 72, 154, 90, 69, 129, 152, 24, 241, 42, 31, 232, 72, 44, 139, 58, 222, 212, 249, 30, 228, 184, 123, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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: