Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d24b30e80f68bc1947d94a38f7a74afe3aa3c5768620da2ac2d3604c0874c74

Tx prefix hash: 85b5e356fc561e4ec76e34d1f8b92eeb6c5a36fd8297974ff68f63fe72884dba
Tx public key: a7530eacd90ae3b2c73ebb9b9468f226528d7dfc1b7c3ec26966feb8f3bd59e6
Timestamp: 1650706890 Timestamp [UTC]: 2022-04-23 09:41:30 Age [y:d:h:m:s]: 04:213:04:29:52
Block: 486300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1197159 RingCT/type: yes/0
Extra: 01a7530eacd90ae3b2c73ebb9b9468f226528d7dfc1b7c3ec26966feb8f3bd59e602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.015021331359 xmr

stealth address amount amount idx tag
00: 91f19ade79641f4ab98e1a07d71c59d2aa99721509e77bfbad316e2339325e16 0.015021331359 908553 of 0 -

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": 486310, "vin": [ { "gen": { "height": 486300 } } ], "vout": [ { "amount": 15021331359, "target": { "key": "91f19ade79641f4ab98e1a07d71c59d2aa99721509e77bfbad316e2339325e16" } } ], "extra": [ 1, 167, 83, 14, 172, 217, 10, 227, 178, 199, 62, 187, 155, 148, 104, 242, 38, 82, 141, 125, 252, 27, 124, 62, 194, 105, 102, 254, 184, 243, 189, 89, 230, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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: