Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb45e43b49f07152fdbd1f2ceb2c811aa43dc08d6cc366af51732439433ed045

Tx prefix hash: 3162dc3ec62e3ea014e874911b238c97055d1e3f77d0b57ce5afcc1bb48baf0f
Tx public key: e29028e9403c37c2a445b4dafa820354b321154d036f209d2915252a3560bced
Timestamp: 1772656397 Timestamp [UTC]: 2026-03-04 20:33:17 Age [y:d:h:m:s]: 00:255:02:49:12
Block: 1490733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187744 RingCT/type: yes/0
Extra: 01e29028e9403c37c2a445b4dafa820354b321154d036f209d2915252a3560bced021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a6fd6e9144c5b8e7124db01beb2588c7bed0c08a7137c0883d0a9e13a62b84a 0.000600000000 1980243 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": 1490743, "vin": [ { "gen": { "height": 1490733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6fd6e9144c5b8e7124db01beb2588c7bed0c08a7137c0883d0a9e13a62b84a" } } ], "extra": [ 1, 226, 144, 40, 233, 64, 60, 55, 194, 164, 69, 180, 218, 250, 130, 3, 84, 179, 33, 21, 77, 3, 111, 32, 157, 41, 21, 37, 42, 53, 96, 188, 237, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: