Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb5522d2d5c9e109d1a6b66b6cb42615f073e79434cf768d28a7db8d89352f7b

Tx prefix hash: 65f10c637f89dc7a8108c1437fa4cbb627db5a8677b43805b1fe93c6cca7bb60
Tx public key: 074a49c14126c60312ed86a2096b222914f875e5dc6515c1fc145d66cae3a36a
Timestamp: 1772400711 Timestamp [UTC]: 2026-03-01 21:31:51 Age [y:d:h:m:s]: 00:263:23:33:56
Block: 1488613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194323 RingCT/type: yes/0
Extra: 01074a49c14126c60312ed86a2096b222914f875e5dc6515c1fc145d66cae3a36a021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2070fd1e294e105d9d772655ef824211fd6bfe410c733e9a3468e3db1317a9bd 0.000600000000 1978093 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": 1488623, "vin": [ { "gen": { "height": 1488613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2070fd1e294e105d9d772655ef824211fd6bfe410c733e9a3468e3db1317a9bd" } } ], "extra": [ 1, 7, 74, 73, 193, 65, 38, 198, 3, 18, 237, 134, 162, 9, 107, 34, 41, 20, 248, 117, 229, 220, 101, 21, 193, 252, 20, 93, 102, 202, 227, 163, 106, 2, 17, 0, 0, 0, 5, 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: