Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ef1dd3e6897bda3edc8a880f7bf075ba0530722b1e890a3a6a7c6f74397ab38

Tx prefix hash: 722cc1d543dd5f66a29f2a90d52fb8125260852acf7e9a0870b75f3ad32619bb
Tx public key: 152cd415ad52da81c8dac9fd1e89e584dd0012f5799d33bca3811073403370d0
Timestamp: 1745477431 Timestamp [UTC]: 2025-04-24 06:50:31 Age [y:d:h:m:s]: 01:207:14:14:17
Block: 1268264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412378 RingCT/type: yes/0
Extra: 01152cd415ad52da81c8dac9fd1e89e584dd0012f5799d33bca3811073403370d00211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5239fbd49a54036a3e5f650ca897b915fbf17810f5a8c1378efb1d0dbba06fd9 0.000600000000 1755493 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": 1268274, "vin": [ { "gen": { "height": 1268264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5239fbd49a54036a3e5f650ca897b915fbf17810f5a8c1378efb1d0dbba06fd9" } } ], "extra": [ 1, 21, 44, 212, 21, 173, 82, 218, 129, 200, 218, 201, 253, 30, 137, 229, 132, 221, 0, 18, 245, 121, 157, 51, 188, 163, 129, 16, 115, 64, 51, 112, 208, 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: