Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6358afec0f157a40d232abbd690ecffec2bb5198ecdbd138b0d9a4bc013cd127

Tx prefix hash: b3ee27e92d73c665d57072064fa35b4a809a93f14e7dddd44578d9a50149c4ac
Tx public key: 587bf4c9a43ef3a981f22a4dca21eb109d6415f8c47d5ad95437ba0c15535a93
Timestamp: 1770995055 Timestamp [UTC]: 2026-02-13 15:04:15 Age [y:d:h:m:s]: 00:275:14:16:08
Block: 1477004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202424 RingCT/type: yes/0
Extra: 01587bf4c9a43ef3a981f22a4dca21eb109d6415f8c47d5ad95437ba0c15535a93021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dbd493ee90b00fe65d18566f5a71b4dfb970a2ca04791ec64febf1a266b4250b 0.000600000000 1966316 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": 1477014, "vin": [ { "gen": { "height": 1477004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbd493ee90b00fe65d18566f5a71b4dfb970a2ca04791ec64febf1a266b4250b" } } ], "extra": [ 1, 88, 123, 244, 201, 164, 62, 243, 169, 129, 242, 42, 77, 202, 33, 235, 16, 157, 100, 21, 248, 196, 125, 90, 217, 84, 55, 186, 12, 21, 83, 90, 147, 2, 17, 0, 0, 0, 8, 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: