Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a68f130b311efea8ca107fabeb39c9a8e4fe90a1bae4499c0971da634f090efd

Tx prefix hash: 8cbb079a92e39692b8efc4116112feb32b5ef5d6e69c531a754d1b581349116b
Tx public key: 30936172f787f6ce87f0c70087f8c3a38fbc733f3eb8b512d309e95e066947bc
Timestamp: 1773941201 Timestamp [UTC]: 2026-03-19 17:26:41 Age [y:d:h:m:s]: 00:243:02:53:51
Block: 1501374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179242 RingCT/type: yes/0
Extra: 0130936172f787f6ce87f0c70087f8c3a38fbc733f3eb8b512d309e95e066947bc021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 46cc427145fc243f9d86cec0e20f347ef418a5af7ac3f2d2c430cf7f4c1575ae 0.000600000000 1991058 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": 1501384, "vin": [ { "gen": { "height": 1501374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46cc427145fc243f9d86cec0e20f347ef418a5af7ac3f2d2c430cf7f4c1575ae" } } ], "extra": [ 1, 48, 147, 97, 114, 247, 135, 246, 206, 135, 240, 199, 0, 135, 248, 195, 163, 143, 188, 115, 63, 62, 184, 181, 18, 211, 9, 233, 94, 6, 105, 71, 188, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: