Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030d14bfddce7af14f6f2fbf5d15c0440a4f1d16d37bd79c5d6f749aa9edfb6e

Tx prefix hash: 7c84cde9c9e651fb150b3b453f6eace5322e433bff3d6b4ba1e5902c5352fd4f
Tx public key: 379faf04ccdaccff4a905db8e21bfdb869e5779b3d81ad6eadaa80e09ed7db54
Timestamp: 1742001328 Timestamp [UTC]: 2025-03-15 01:15:28 Age [y:d:h:m:s]: 01:248:08:49:13
Block: 1239507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441547 RingCT/type: yes/0
Extra: 01379faf04ccdaccff4a905db8e21bfdb869e5779b3d81ad6eadaa80e09ed7db54021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0df83cc0e1b26b45afd4686e73047b037c7fd26ad13d0e24e7d8a78d945cdfe8 0.000600000000 1726472 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": 1239517, "vin": [ { "gen": { "height": 1239507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0df83cc0e1b26b45afd4686e73047b037c7fd26ad13d0e24e7d8a78d945cdfe8" } } ], "extra": [ 1, 55, 159, 175, 4, 204, 218, 204, 255, 74, 144, 93, 184, 226, 27, 253, 184, 105, 229, 119, 155, 61, 129, 173, 110, 173, 170, 128, 224, 158, 215, 219, 84, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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: