Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba674f058147261ef6ed6a7b4b4b634bd605567d9dd07d642bc9bc36b8db2e50

Tx prefix hash: f7180fddf131d980ce6f025f42f4a3dc950afc2b234e0e8451a24e3e9fefea57
Tx public key: 30cc0f932db27753c4b727add913b338451cbb2aadc7e52671ef10c85e3b5a53
Timestamp: 1772972444 Timestamp [UTC]: 2026-03-08 12:20:44 Age [y:d:h:m:s]: 00:257:12:42:57
Block: 1493359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189702 RingCT/type: yes/0
Extra: 0130cc0f932db27753c4b727add913b338451cbb2aadc7e52671ef10c85e3b5a53021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 12119d319d2a9a4c4a2779cea1cb7183b8a57c595317c656c73bdf266f37df0a 0.000600000000 1982915 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": 1493369, "vin": [ { "gen": { "height": 1493359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12119d319d2a9a4c4a2779cea1cb7183b8a57c595317c656c73bdf266f37df0a" } } ], "extra": [ 1, 48, 204, 15, 147, 45, 178, 119, 83, 196, 183, 39, 173, 217, 19, 179, 56, 69, 28, 187, 42, 173, 199, 229, 38, 113, 239, 16, 200, 94, 59, 90, 83, 2, 17, 0, 0, 0, 3, 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: