Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 588bf9fddc8046be5e1262bb5d21a024e3566c2a68134fe9e40ddf68e8e25b3e

Tx prefix hash: 164d9dba40622e7122011c942a0cba5989e61cbf1c8f5f75ca2274058a957f82
Tx public key: 0925a165dbeebff96b3129402abe0afd478000566f5c07940ec3386ea28a893b
Timestamp: 1758407219 Timestamp [UTC]: 2025-09-20 22:26:59 Age [y:d:h:m:s]: 01:061:22:52:55
Block: 1372861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310633 RingCT/type: yes/0
Extra: 010925a165dbeebff96b3129402abe0afd478000566f5c07940ec3386ea28a893b021100000001ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3b2c9dcc805a0fbbeba6a84b9e86392b154c632cbf35b871ecf193b214901e23 0.000600000000 1860946 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": 1372871, "vin": [ { "gen": { "height": 1372861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b2c9dcc805a0fbbeba6a84b9e86392b154c632cbf35b871ecf193b214901e23" } } ], "extra": [ 1, 9, 37, 161, 101, 219, 238, 191, 249, 107, 49, 41, 64, 42, 190, 10, 253, 71, 128, 0, 86, 111, 92, 7, 148, 14, 195, 56, 110, 162, 138, 137, 59, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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: