Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c79bb7c141c565d2aea9fe49beb91add359d669c46485642eea4ceadad692832

Tx prefix hash: a60fa1db5c5c7606caea0020958a04aa0f52d1d36153611e561db2b70587603b
Tx public key: 0fe912d586cd343b4028b655ba5e524ba522bc1229a0eb5e3345761a5c33dc09
Timestamp: 1774839187 Timestamp [UTC]: 2026-03-30 02:53:07 Age [y:d:h:m:s]: 00:233:19:40:44
Block: 1508790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172648 RingCT/type: yes/0
Extra: 010fe912d586cd343b4028b655ba5e524ba522bc1229a0eb5e3345761a5c33dc09021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 35b0f67b781982ff602f20040f333e66e2e8c1ca9e1d651a1828f7da8123a37b 0.000600000000 1998544 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": 1508800, "vin": [ { "gen": { "height": 1508790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35b0f67b781982ff602f20040f333e66e2e8c1ca9e1d651a1828f7da8123a37b" } } ], "extra": [ 1, 15, 233, 18, 213, 134, 205, 52, 59, 64, 40, 182, 85, 186, 94, 82, 75, 165, 34, 188, 18, 41, 160, 235, 94, 51, 69, 118, 26, 92, 51, 220, 9, 2, 17, 0, 0, 0, 7, 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: