Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce04bf54a67cacbec30f7a6ec0858c007830a0ddacd3f5cc5333c9a69d1e7e73

Tx prefix hash: 6b7c524a16bfcf7b53b291a046bdd9d8d642848138578613405d11dd1075e9b6
Tx public key: 89e5b140d66392322a5951a7d3bd916377cb5d1140fb709aded908a022a8a5e5
Timestamp: 1767230353 Timestamp [UTC]: 2026-01-01 01:19:13 Age [y:d:h:m:s]: 00:062:14:03:26
Block: 1445979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 44606 RingCT/type: yes/0
Extra: 0189e5b140d66392322a5951a7d3bd916377cb5d1140fb709aded908a022a8a5e5020900000007f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bcfe03829b28f6ba974f4d7c41d043a2b6efe500447aebe6cafd32b7b91296a1 0.000600000000 1934927 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": 1445989, "vin": [ { "gen": { "height": 1445979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcfe03829b28f6ba974f4d7c41d043a2b6efe500447aebe6cafd32b7b91296a1" } } ], "extra": [ 1, 137, 229, 177, 64, 214, 99, 146, 50, 42, 89, 81, 167, 211, 189, 145, 99, 119, 203, 93, 17, 64, 251, 112, 154, 222, 217, 8, 160, 34, 168, 165, 229, 2, 9, 0, 0, 0, 7, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369