Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a449d1285ce9a20a7fd0a3a241cbf04b0c3af352974fd1b0ec4743ca7ca8c806

Tx prefix hash: 2c56eb01fd7abc87ad4ac9200d1e9fbf16f64666fd8321cb59c5e5f6ae964b98
Tx public key: 13b88a5b2c80dcb977fca57a2d590b708f6da8c27b20034a2be6ab857df83493
Timestamp: 1771453765 Timestamp [UTC]: 2026-02-18 22:29:25 Age [y:d:h:m:s]: 00:276:05:42:09
Block: 1480781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202713 RingCT/type: yes/0
Extra: 0113b88a5b2c80dcb977fca57a2d590b708f6da8c27b20034a2be6ab857df83493021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 456f27b94fc3510eb1389a6adf7ee4264b8093a88a2d219304530e7cdfa9afbc 0.000600000000 1970151 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": 1480791, "vin": [ { "gen": { "height": 1480781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "456f27b94fc3510eb1389a6adf7ee4264b8093a88a2d219304530e7cdfa9afbc" } } ], "extra": [ 1, 19, 184, 138, 91, 44, 128, 220, 185, 119, 252, 165, 122, 45, 89, 11, 112, 143, 109, 168, 194, 123, 32, 3, 74, 43, 230, 171, 133, 125, 248, 52, 147, 2, 17, 0, 0, 0, 2, 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: