Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68b71214226f70e97be243d1742ed7ce3e9ef337c2cfd2da5d21631f65842bf8

Tx prefix hash: 8882e3935059db081470a2a30e796c577e4dbd88c8f9f97edd56e430c5d33b52
Tx public key: b4feb4e636a98a556c00c3902969d246c4e2b6b236cc5f6c53b0fbfd11eaa43b
Timestamp: 1718752242 Timestamp [UTC]: 2024-06-18 23:10:42 Age [y:d:h:m:s]: 02:155:18:31:00
Block: 1047212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636282 RingCT/type: yes/0
Extra: 01b4feb4e636a98a556c00c3902969d246c4e2b6b236cc5f6c53b0fbfd11eaa43b0211000000010bba16d7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 73e582137dea19a7d2a4d8412296269e18b0fc5c69341f148918176062dd22ab 0.000600000000 1517031 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": 1047222, "vin": [ { "gen": { "height": 1047212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73e582137dea19a7d2a4d8412296269e18b0fc5c69341f148918176062dd22ab" } } ], "extra": [ 1, 180, 254, 180, 230, 54, 169, 138, 85, 108, 0, 195, 144, 41, 105, 210, 70, 196, 226, 182, 178, 54, 204, 95, 108, 83, 176, 251, 253, 17, 234, 164, 59, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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: