Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7a9ad2b98fc0ccf65e3f2fcae5b6ae2511c4c2615f6257503c2da805976716d

Tx prefix hash: 5b45de2e51596633f12a5631414d60df58ff950839086b3870d53895cb9ef54a
Tx public key: 452a2ff1e8a3aa1135be60af12b38242844a7536b257a8f7e4ec53e18893a9f2
Timestamp: 1747321252 Timestamp [UTC]: 2025-05-15 15:00:52 Age [y:d:h:m:s]: 00:362:08:56:23
Block: 1283534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248912 RingCT/type: yes/0
Extra: 01452a2ff1e8a3aa1135be60af12b38242844a7536b257a8f7e4ec53e18893a9f20211000000079f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0b7dfee3861c07a3608268b51981afb8f2a91abaf06ab0cc35490eee0f49a492 0.000600000000 1770953 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": 1283544, "vin": [ { "gen": { "height": 1283534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b7dfee3861c07a3608268b51981afb8f2a91abaf06ab0cc35490eee0f49a492" } } ], "extra": [ 1, 69, 42, 47, 241, 232, 163, 170, 17, 53, 190, 96, 175, 18, 179, 130, 66, 132, 74, 117, 54, 178, 87, 168, 247, 228, 236, 83, 225, 136, 147, 169, 242, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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: