Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63716164f745677345db67136512debc0e149f579e13a164a90be48e823ec6b0

Tx prefix hash: 40ff0fc5bc3bc61bd58eed342686dba0eb9ec8ad74ea1f4861401dcb41939c84
Tx public key: e9e7768ad134f1ed12bdd76b82379d795d54e0f3ce3d5c3ca0c2ae0a10e0020e
Timestamp: 1673496901 Timestamp [UCT]: 2023-01-12 04:15:01 Age [y:d:h:m:s]: 02:097:10:41:51
Block: 672877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591340 RingCT/type: yes/0
Extra: 01e9e7768ad134f1ed12bdd76b82379d795d54e0f3ce3d5c3ca0c2ae0a10e0020e0211000000018b7b6602000000000000000000

1 output(s) for total of 3.618088015000 dcy

stealth address amount amount idx
00: 440a80d6a8cfced18960f9c6dd98ffdf36e893dddcc3cbfbc3ea9e4a12530f48 3.618088015000 1114446 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 dinasty-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": 672887, "vin": [ { "gen": { "height": 672877 } } ], "vout": [ { "amount": 3618088015, "target": { "key": "440a80d6a8cfced18960f9c6dd98ffdf36e893dddcc3cbfbc3ea9e4a12530f48" } } ], "extra": [ 1, 233, 231, 118, 138, 209, 52, 241, 237, 18, 189, 215, 107, 130, 55, 157, 121, 93, 84, 224, 243, 206, 61, 92, 60, 160, 194, 174, 10, 16, 224, 2, 14, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8