Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1970f74d90a2f7d77a02c21fcaae78f96cf96fa5fec9cbdae0c453197fec5ecf

Tx prefix hash: 1a76b31b04acb41b4ee94a83be61413a2050e8c9631947c472ad093fae019dca
Tx public key: 8beaa77235dbe6702cb2a9d0bc4d8e4b9c5189c68ed71407ebcb0d7c4adae986
Timestamp: 1771301843 Timestamp [UTC]: 2026-02-17 04:17:23 Age [y:d:h:m:s]: 00:273:07:18:00
Block: 1479510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200839 RingCT/type: yes/0
Extra: 018beaa77235dbe6702cb2a9d0bc4d8e4b9c5189c68ed71407ebcb0d7c4adae986021100000011f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 740decab9e0be5e07ce874137ebba19bf3960756fa1960af64d3064aa1fd1116 0.000600000000 1968860 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": 1479520, "vin": [ { "gen": { "height": 1479510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "740decab9e0be5e07ce874137ebba19bf3960756fa1960af64d3064aa1fd1116" } } ], "extra": [ 1, 139, 234, 167, 114, 53, 219, 230, 112, 44, 178, 169, 208, 188, 77, 142, 75, 156, 81, 137, 198, 142, 215, 20, 7, 235, 203, 13, 124, 74, 218, 233, 134, 2, 17, 0, 0, 0, 17, 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: