Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 769b445cc57423500b605720dd3aa85eac719a4d6faf272fecf92741a5233dd2

Tx prefix hash: 42014f1a0e44c3ccb46ca7f5eb89c326a6b21584c22dc6a1b486f03495ef38cb
Tx public key: c18afabdc5b3ffdd7c4c558f2fb5618fc703af8e39cbdcd5a300988862c53d1e
Timestamp: 1580629231 Timestamp [UTC]: 2020-02-02 07:40:31 Age [y:d:h:m:s]: 06:295:03:29:26
Block: 57054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1626440 RingCT/type: yes/0
Extra: 01c18afabdc5b3ffdd7c4c558f2fb5618fc703af8e39cbdcd5a300988862c53d1e021137b7479e00000000000000000000000000

1 output(s) for total of 0.397159311208 xmr

stealth address amount amount idx tag
00: f9efbcb9db02847d270a8bd16c97aa57fb39122d084af7ab2e0560c1fd47a729 0.397159311208 105171 of 0 -

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": 57064, "vin": [ { "gen": { "height": 57054 } } ], "vout": [ { "amount": 397159311208, "target": { "key": "f9efbcb9db02847d270a8bd16c97aa57fb39122d084af7ab2e0560c1fd47a729" } } ], "extra": [ 1, 193, 138, 250, 189, 197, 179, 255, 221, 124, 76, 85, 143, 47, 181, 97, 143, 199, 3, 175, 142, 57, 203, 220, 213, 163, 0, 152, 136, 98, 197, 61, 30, 2, 17, 55, 183, 71, 158, 0, 0, 0, 0, 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: