Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc506a6e0bcc2ab31dc28cfcd71d42b53a65a169c4a7b4e10938b8f0ab18d386

Tx prefix hash: 3cd0c908697215573678bd9ea01af383e157aa8ae99fca0bb206dc6070fa9150
Tx public key: 32a949fd636b928d4432ddf8634355dd66d742d6e11918b1a11d96b1e89abd15
Timestamp: 1772141710 Timestamp [UTC]: 2026-02-26 21:35:10 Age [y:d:h:m:s]: 00:263:17:47:24
Block: 1486466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193997 RingCT/type: yes/0
Extra: 0132a949fd636b928d4432ddf8634355dd66d742d6e11918b1a11d96b1e89abd1502110000000ce4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cbf5343ad5d10e20b73728849d746eeeec802e7e4519150737c9b7d6e2c1d165 0.000600000000 1975920 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": 1486476, "vin": [ { "gen": { "height": 1486466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbf5343ad5d10e20b73728849d746eeeec802e7e4519150737c9b7d6e2c1d165" } } ], "extra": [ 1, 50, 169, 73, 253, 99, 107, 146, 141, 68, 50, 221, 248, 99, 67, 85, 221, 102, 215, 66, 214, 225, 25, 24, 177, 161, 29, 150, 177, 232, 154, 189, 21, 2, 17, 0, 0, 0, 12, 228, 245, 25, 63, 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: