Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0612523d477ab94938b49aec7d72bd448a2f81850b76823cef2e84a4b5e3933

Tx prefix hash: 2b75deaf1f22402b7f7a6b76781a5e8ca6cb8694606ff130558e71defb0a9dcd
Tx public key: e52442eebc389414763de2282252e01128af3e0abdebe9de71c79a4dbd36a5c3
Timestamp: 1774876382 Timestamp [UTC]: 2026-03-30 13:13:02 Age [y:d:h:m:s]: 00:237:09:57:15
Block: 1509104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175046 RingCT/type: yes/0
Extra: 01e52442eebc389414763de2282252e01128af3e0abdebe9de71c79a4dbd36a5c3021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2de32c72f11b76de3c9456a8c61ef14a270f7e220a70aa58765701d46ed7b7b7 0.000600000000 1998860 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": 1509114, "vin": [ { "gen": { "height": 1509104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2de32c72f11b76de3c9456a8c61ef14a270f7e220a70aa58765701d46ed7b7b7" } } ], "extra": [ 1, 229, 36, 66, 238, 188, 56, 148, 20, 118, 61, 226, 40, 34, 82, 224, 17, 40, 175, 62, 10, 189, 235, 233, 222, 113, 199, 154, 77, 189, 54, 165, 195, 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: