Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 853b36e01aed58e4f90bdfa0237268c47a66a80922eca5e5ce04bf8e6a5b32c6

Tx prefix hash: 717eac447066c9696baa1ed3d78973c364efb293e81e04e21bb2a46a0ae6d4de
Tx public key: d76968952b19215060bcde02669e4108b5e31bad70cc4eaaf449d1601081c5e6
Timestamp: 1656975684 Timestamp [UCT]: 2022-07-04 23:01:24 Age [y:d:h:m:s]: 03:126:12:42:14
Block: 536749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 870165 RingCT/type: yes/0
Extra: 01d76968952b19215060bcde02669e4108b5e31bad70cc4eaaf449d1601081c5e60211000000012e6b1fd5000000000000000000

1 output(s) for total of 10.221812246000 dcy

stealth address amount amount idx
00: 1e364a46e6fcc10717b720929acb808f9d57353e51deb634a4b37f1dab46ee1f 10.221812246000 966548 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": 536759, "vin": [ { "gen": { "height": 536749 } } ], "vout": [ { "amount": 10221812246, "target": { "key": "1e364a46e6fcc10717b720929acb808f9d57353e51deb634a4b37f1dab46ee1f" } } ], "extra": [ 1, 215, 105, 104, 149, 43, 25, 33, 80, 96, 188, 222, 2, 102, 158, 65, 8, 181, 227, 27, 173, 112, 204, 78, 170, 244, 73, 209, 96, 16, 129, 197, 230, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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