Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ac6aa3368df0f94b6615e4ba8664491bdff51e91c0917c0ed95a6e32cc0e70e

Tx prefix hash: de2c9c2f05cbceb45ed25e29dcefe40b109c3a47ce255a476ec1b5667bbf1269
Tx public key: e464f31ce5ef42b50b6161845d0d33e0ba33d19fb3301d6a43cf8dd216eb4800
Timestamp: 1686461049 Timestamp [UCT]: 2023-06-11 05:24:09 Age [y:d:h:m:s]: 02:148:06:21:08
Block: 779764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 625706 RingCT/type: yes/0
Extra: 01e464f31ce5ef42b50b6161845d0d33e0ba33d19fb3301d6a43cf8dd216eb480002110000000275e3f0e9000000000000000000

1 output(s) for total of 1.600730913000 dcy

stealth address amount amount idx
00: 08bc30acbc45c4434fa5076503d6150183793e7fe5b76679821b1cab5f6aea94 1.600730913000 1229439 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": 779774, "vin": [ { "gen": { "height": 779764 } } ], "vout": [ { "amount": 1600730913, "target": { "key": "08bc30acbc45c4434fa5076503d6150183793e7fe5b76679821b1cab5f6aea94" } } ], "extra": [ 1, 228, 100, 243, 28, 229, 239, 66, 181, 11, 97, 97, 132, 93, 13, 51, 224, 186, 51, 209, 159, 179, 48, 29, 106, 67, 207, 141, 210, 22, 235, 72, 0, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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