Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15b0e056fab6343ca45150a912270bb8d41916de6340a2e4ce75f070b0dd8d4e

Tx prefix hash: 01536f8d0500c65b3a33d3695c79cc2b4bd888c155b18aeed80b2b9a47e3dd4b
Tx public key: be5b93c53ede711d70399f0abf520ae9b6db3d95ad4c090bfb58fb2b11836072
Timestamp: 1744955742 Timestamp [UTC]: 2025-04-18 05:55:42 Age [y:d:h:m:s]: 01:027:10:30:08
Block: 1263944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270528 RingCT/type: yes/0
Extra: 01be5b93c53ede711d70399f0abf520ae9b6db3d95ad4c090bfb58fb2b118360720211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 74b9571ff34c93783f2ad3a11ddc09d2ac03e0663c9adc2bf6eb6c4c728f4594 0.000600000000 1751137 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": 1263954, "vin": [ { "gen": { "height": 1263944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74b9571ff34c93783f2ad3a11ddc09d2ac03e0663c9adc2bf6eb6c4c728f4594" } } ], "extra": [ 1, 190, 91, 147, 197, 62, 222, 113, 29, 112, 57, 159, 10, 191, 82, 10, 233, 182, 219, 61, 149, 173, 76, 9, 11, 251, 88, 251, 43, 17, 131, 96, 114, 2, 17, 0, 0, 0, 1, 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: