Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b479e31972f7a4936729775ee0cdfa3e6f0e88b4273b87201acf4b15f5fec0b4

Tx prefix hash: a1f5d8a22d2f20fe3408f96792d58eabcd314e9f3117bede03966af3a3c7e2e5
Tx public key: 00b135b35612200791e744108efe71bd24e8e0e842c9410e306952162f2c15f4
Timestamp: 1769420070 Timestamp [UTC]: 2026-01-26 09:34:30 Age [y:d:h:m:s]: 00:298:20:29:01
Block: 1463938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219275 RingCT/type: yes/0
Extra: 0100b135b35612200791e744108efe71bd24e8e0e842c9410e306952162f2c15f402110000000449d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1f9c2eeefa119fd630086e9ea1338b52a33b791824d1675b6b3239d27654f306 0.000600000000 1953154 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": 1463948, "vin": [ { "gen": { "height": 1463938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f9c2eeefa119fd630086e9ea1338b52a33b791824d1675b6b3239d27654f306" } } ], "extra": [ 1, 0, 177, 53, 179, 86, 18, 32, 7, 145, 231, 68, 16, 142, 254, 113, 189, 36, 232, 224, 232, 66, 201, 65, 14, 48, 105, 82, 22, 47, 44, 21, 244, 2, 17, 0, 0, 0, 4, 73, 215, 62, 152, 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: